[drupal-devel] [feature] AJAX form_autocomplete() field

[moshe weitzman]

Issue status update for http://drupal.org/node/22519

 Project:      Drupal
 Version:      4.6.0
 Component:    base system
 Category:     feature requests
 Priority:     normal
 Assigned to:  Anonymous
 Reported by:  Thox
 Updated by:   moshe weitzman
 Status:       patch

one more nit - pressing escape should ideally caused tghe autocomplete
div to disappear. sometimes it is not wanted.


please submit a patch against HEAD, if possible.




moshe weitzman



Previous comments:
------------------------------------------------------------------------

May 10, 2005 - 10:29 : Thox

Attachment: http://drupal.org/files/issues/form_autocomplete.patch (11.48 KB)

As discussed on #drupal, I've created a patch to add an AJAX-based
form_autocomplete() field to the Drupal core.


The documentation of the autocomplete callback remains undocumented.
See http://drupal.org/node/22471 for more details.




------------------------------------------------------------------------

May 10, 2005 - 14:18 : Thox

I've created a demonstration page that works in a number of different
browsers:


http://brandedthoughts.co.uk/node/62




------------------------------------------------------------------------

May 10, 2005 - 15:50 : Dries

Works on Firefox @ MacOS.




------------------------------------------------------------------------

May 10, 2005 - 18:14 : solon

Don't mean to throw a spanner in the works, but I get an error if the
request I type does not match any in the database/ file it is looking
through.
-- Begin Error --
JavaScript
An HTTP error undefined occured.
http://brandedthoughts.co.uk/recipe/ingredient/autocomplete
-- End Error --


Would it be best to have it display an ' informative' error message, or
stop trying to 'guess' if it definately can't find a match?


BTW: I am using Safari 2.0 Mac OsX (you don't say :P )




------------------------------------------------------------------------

May 10, 2005 - 19:16 : solon

The error no longer shows, so that issue seems to be fixed (in Safari 2
anyway. As far as I can tell, this is the only browser that it occcured
in).