I just wanted to followup with my workaround for others.
Firstly one could override assets, or at least this asset, using the
classpath. Eg. createing your own
src/main/resources/org/apache/tapestry5/corelib/mixins/autocompelte.js
would cause it to get loaded instead of tapestrys.
However, I looked into first upgrading to the latest (1.8.2/1.6.0.3)
release. Just place all files on your classpath (I used
src/main/resources/com/xxyy/scriptaculous_1_8_2/) and add the following to
your module in contributeApplicationDefaults:
configuration.add("tapestry.scriptaculous",
"classpath:com/xxyy/scriptaculous_1_8_2/");
By all files I mean the deployed .js including prototype and not just the
src js from scriptaculous.
This release did not help with the autocompleter issue in IE; so I
researched into using the patch outlined by jrochkind in
http://prototype.lighthouseapp.com/projects/8887/tickets/32-ajax-autocomplete-in-ie-with-doctype
prototyp ticket 32 replacing
"var offsetParent = element.getOffsetParent();"
with
"var offsetParent = (element.parent) ? element.getOffsetParent() : 0;"
in prototype.js in the above override directory.
And voila my users are happy. Autocomplete and what other things I use work
fine.
There could be other sideaffects so use normal caution using this patch and
monitor to see if there is a newer release of prototype or scriptaculous.
Hope this helps someone else, and please let me know if there are better
solutions!
--
View this message in context:
http://www.nabble.com/Autocomplete-problems-in-IE-tp22524872p22553376.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
