On Sat, 28 Feb 2009 01:11:15 +0100, Howard Lewis Ship <hls...@gmail.com> wrote:
> The > end result it that you can "outrace" Tapestry, click a link that > should update a zone and get incorrect behavior or even a runtime > exception. I actually see this when using Formo's time-tracking > application from home through a slow pipe, exacerbated by HTTPS, where > I get the error that "Block is not a valid response type". What should > have been an Ajax request was processed instead as a traditional page > render request, because the JavaScript was not ready. > > An earlier version of Tapestry 5 approached this problem by disabling > the link components when the zone parameter was in use; that is, the > href parameter was written out a "#", so the only way the link would > be active is via an attached onclick event handler. > > This solution was weak, because there was no graceful degradation: > clients without JavaScript would have a non-functioning application. > Thus it was changed to render the href normally AND add an onclick > event handler, which leads to the race conditions described above. I didn't quite understand this part. If a user clicks the link before its onclick handler has been added, wouldn't that result in the same behaviour as having javascript disabled? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
