https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34113
--- Comment #5 from David Cook <[email protected]> --- On a non-Koha project, I just replaced a jQueryUI autocomplete with the Alphagov "accessible-autocomplete", and it went pretty well. The parameters are very similar, and it's pretty easy to style. I like its default styling as well. That said, there is 1 major difference. Instead of binding to an input element, you bind it to a container element and it dynamically creates the input element. Dealing with this difference is probably where most of the work would be, especially for cases where we're using Template::Toolkit to put a value into the "value" attribute for the input. We'll have to do something like put it in a hidden field and then pass it as default value or something using Javascript (which is part of the accessible-autocomplete API). -- The Alphagov folk say that they don't support the autocomplete, but they actively maintain it, and it has current releases. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
