Hi, I have a nice web-app that was a pleasure to write in T5; but am running into problems that I need some help with. The autocomplete mixin works just fine in FF3 etc but there is a issue that seriously affects its usability in IE (I have only tested 7) and end-users are complaining. When typing the autocomplete fails the first time the field is used, only clearing the field and typing again will get autocomplete to work in IE. SO users with IE either think there is no autocomplete or think it is horribly slow and flaky. Its also rather central to my apps utility.
This seams to be a problem with prototype; I found some information and workarounds in other environments, but no fix seams to be in the works. See for instance http://stackoverflow.com/questions/108650/script-aculo-us-autocompleter-problem-in-ie/ for more information. So how can I solve this now in 5.0.18? One option would be to follow the suggested js hack - but how to insert the javascript at the expected place (after or when autocomplete.js gets loaded)? Another is to patch prototype; but how then keep that cleanly separate in my project? Both involve some form of asset overriding that I can figure out how to do without making my own builds of t5-core or prototype. Or perhaps someone has a better solution? An alternative autocomplete component that works in IE? BR Peter -- View this message in context: http://www.nabble.com/Autocomplete-problems-in-IE-tp22524872p22524872.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
