[whatwg] element.onFocus instead of window.onhashcange ?
t.broyer at gmail.com
Thu Nov 19 01:33:25 PST 2009
On Thu, Nov 19, 2009 at 1:38 AM, Dean Edwards wrote:
> On 17/11/2009 15:50, Bjartur Thorlacius wrote:
>> As the discussion had turned into bunch (good) advice giving, I
>> decided to repost this if anyone actually has opinion on this matter
>> and/or could tell me why the spec recommends firing hashchange on the
>> document instead of a specific element when a user navigates to a URI
>> with a hash component.
> A lot of Ajax apps will manipulate the value of location.hash to represent
> the *state of the application*. In this case there is no corresponding
> element to trap the onfocus event.
...and this includes GMail that Bjartur is using (it also includes:
Twitter, Facebook, Google Reader, Google Code Hosting's source
browsing, Google Wave, etc.)
More information about the whatwg