- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 18 Feb 2009 03:25:11 +0000 (UTC)
On Wed, 10 Sep 2008, Kristof Zelechovski wrote: > > I think the main problem here is that we want to package two different > functions into one event. The legitimate use of hash change where it is > used to reveal a bookmark should trigger an event named "reveal" > dispatched to the target anchor and bubbling, where the handler for the > Window object can be specified as BODY[onreveal]. The AJAX abuse where > it is used to change the context of the page, whereas it can be > determined when no corresponding target anchor can be found, should > trigger the hash change notification broadcast to every object of the > active document that registers for it by declaring a handler. Does this > make sense? It seems that using onload="" for the initial setup and onhashchange="" for subsequent updates would most closely match the likely architecture of Web applications. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 17 February 2009 19:25:11 UTC