#12399 closed enhancement (fixed)
Use jQuery UI autocomplete
Reported by: | sbressler | Owned by: | azaozz |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.0 |
Component: | JavaScript | Keywords: | needs-patch jquery, jquery ui, autocomplete, js, bassistance |
Focuses: | Cc: |
Description
Hi, I'm not certain which version of the bassistance autocomplete is currently in trunk (wp-includes/js/jquery), but I was wondering if there were plans to port to the version of autocomplete being added to jQuery UI 1.8 (now in RC2). UI 1.8 should be finished any day now and I imagine it'd be better to use that stable build than a jQuery plugin (as stable as it is). It looks like joern zaefferer contributed to the version in jQuery UI, so I'm sure it's as good if not better.
Also, it seems with the autocomplete now added to trunk that there are two different ones (suggest.js and autocomplete.js). Will the tag suggestion be ported to use the newer autocomplete?
Thanks!
Change History (9)
#2
in reply to:
↑ description
@
15 years ago
Replying to sbressler:
I imagine it'd be better to use that stable build than a jQuery plugin (as stable as it is).
Would you please elaborate about what would be better? Does the current code have problems? Does the current code lack functionality?
#3
@
15 years ago
- Milestone changed from Unassigned to 3.0
Also, it seems with the autocomplete now added to trunk that there are two different ones (suggest.js and autocomplete.js). Will the tag suggestion be ported to use the newer autocomplete?
+1 to this: we should have a single autocomplete/suggest script.
#4
@
15 years ago
We've used suggest.js for a long time. The menus recently introduced autocomplete.js. I'd be fine sticking with suggest.js since we have it working the way we want it.
Here's a demo and documentation of the version of autocomplete being added to jQuery UI: http://jqueryui.com/demos/autocomplete/