Rexbard wrote:
> If you type enough characters to trigger the autocomplete, then type one
> more character, the autocomplete closes and you are not given any
> suggestions.
>
Yup. Its looks nice, but is rather unintuitive. I think one of the other
autocomplete plugins used caching to load a set of proposals when there
were enough characters, and then reduced the selection when the client
enters more characters, without anymore requests. That way it was much
more responsive.
The demo link is missing on the demo page, yet.
Concerning the 'fx'-option of the plugin:
I think it is easier to understand if the client passes a function
instead of some custom object that needs to be parsed. Eg:
$('#element').Autocomple({
fx: function(suggestionBox) { suggestionBox.SlideInUp(400) }
});
This would give the client more control of the animation (like chaining
animations) and he can rely on existing documentation instead of
figuring out how the object passed for fx is parsed. Maybe there is a
way to write this even more comprehensive.
Something concerning the new interface homepage in general:
There seems to be some bugs in different interface plugins (weird
positioning when moving objects out of the window at the bottom, a lot
of flickering here and there) I'd like to report in detail, but the link
to the forum intended for bug reports gives me a 404 error. While you
fix that, you could add the link to the navigation.
-- Jörn
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
