I just spent quite a while tracking down an IE 7 AJAX problem. It
appears if you use eventlink without t:id you can end up with multiple
html elements with an id of eventlink.
The javascript at the end of the file ends up something like this
Tapestry.init({"zone":["contentZone","avstatus","mgTime","avstat","bootlog"],"linkZone":[["eventLink","contentZone","/acuvigil/index.avtabset:clicked/Companies?t:ac=Giant/707"],["eventLink_0","contentZone","/acuvigil/index.avtabset:clicked/Company?t:ac=Giant/707"],["eventLink_1","contentZone","/acuvigil/index.avtabset:clicked/Branch?t:ac=Giant/707"],["eventlink","bootlog","/acuvigil/index.branchdetail.bootlog:reloadBootLog/698?t:ac=Giant/707"]]});
There is a tab component that contains 3 tabs and the ids are named
eventlink, eventlink_0 and eventlink_1. The last tab contains a
component with an eventlink and as you can see it's id is also
eventlink. Oddly enough this works in Safari and Firefox but not IE 7.
Of course I wanted to blame IE but this does not really appear to be
an IE problem.
So the question is should I always code eventlink like
<t:eventLink t:id="reloadBootLog" >stuff</t:eventLink>
instead of
<t:eventLink t:event="reloadBootLog" >stuff</t:eventLink>
or is this really a Tapestry bug?
Thanks
Barry
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
