On 27-Feb-09, at 19:41 , Martin Strand wrote:
On Sat, 28 Feb 2009 01:11:15 +0100, Howard Lewis Ship <hls...@gmail.com
> wrote:
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?
It would have, but with that solution, url's just had http://www.blah.com/context/page/#
as the url to be clicked, which means that non-javascript clients,
treating it as the same as if javascript was disabled, would try to
access the in-page anchor "", which clearly doesn't exist. It would
amount to a page refresh, and on some browsers not even that, since
the browser would cache the page since you're not going anywhere. So
for non-js or js-disabled clients, you need a real URL.
christian.
Christian Edward Gruber
e-mail: christianedwardgru...@gmail.com
weblog: http://www.geekinasuit.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
