|
Andy, I already pointed out this problem, that doesnt seem to be browser related, but merely due to T5 conception. Basically Howard answered that on a div refresh, the id of the refreshed elements nested in that div are changed by T5 : a timestamp based code is added, making them unique among the client DOM. If this div contains itself another div, pointed by a link, then that link is lost. It explains the page refresh, since your action link (or event link) points to nothing. Howard didnt make any clear statement about that, but it seems to me that nesting Zones is not legal in T5, or at least needs some patching in order to work properly. José Andy Blower a écrit : --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]Rather than explain (probably badly) exactly what the problem is, I'll provide a small example page called BasicAJAX. This page demonstrates that if an actionlink that causes a zone refresh via AJAX is part of the refreshed zone itself, it only works on alternate clicks in IE. Each time it's rendered as part of the zone update it causes a full page refresh when clicked, which means it can do a zone update the following click. It works fine in Firefox though. |
- T5: AJAX Zone updating doesn't work correctly in IE Andy Blower
- Re: T5: AJAX Zone updating doesn't work correctly in IE José Paumard
- RE: T5: AJAX Zone updating doesn't work correctly i... Blower, Andy
- RE: T5: AJAX Zone updating doesn't work correct... Blower, Andy
- Re: T5: AJAX Zone updating doesn't work cor... Josh Canfield
