Am 21.01.2013 09:48, schrieb Robert Vogel:
Hi Krinkle!
Thanks for the clarification!
mediawiki.searchSuggest does NOT use jquery.ui.autocomplete.
Yes, I know. I never said anything like this. Maybe this was a misunderstanding. I said I wanted to replace "mediawiki.searchSuggest" with my own implementation _based on_ "jquery.ui.autocomplete". As "jquery.ui.autocomplete" is delivered together with MW and can easily be made available on the client side thanks to ResourceLoader and its dependency management it was a good choice for me.
Instead you'd register your own module with its own name and make sure it is loaded instead of some other module. The method used can differ based on the feature at hand, but handling this at the module level is not the way to go.
Yes I understand this. And I think this was my problem. I did not find a proper way to "make sure it is loaded instead of some other module", because 'mediawiki.searchSuggest' module is added by OutputPage and there seems to be no way (but changing the current users settings as Matt suggested) to avoid that.
I ran into big problems when using jquery.ui.autocomplete. Xes, I _do_ know how to use it and have years of bad experience with it.
_It is difficult to customise and creates more overhead than it claims to save_ -- especially when you need to modify the suggestion output according to your needs -- , and my advice for MediaWiki is, _not_ to go this way.
My advice: stick on using the current version.
Major problems into which you may run are [1-3].
- customising suggestion output (when you want to use HTML, when you want to highlight something in the suggestions): very difficult, lot of overhead - when leaving the tab and returning. the suggestion list disappears. Retriggering onfocus is almost impossible without negative side-effects.
Tom [1] https://forum.jquery.com/topic/jquery-ui-autocomplete-bug-autocomplete-sugge... [2] https://forum.jquery.com/topic/autocomplete-ie7-backspace-issue#147370000025... [3] bugs.jqueryui.com/ticket/8832