W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2007

[whatwg] hashchange only dispatched in history traversal

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 14 Aug 2007 10:15:48 +0000 (UTC)
Message-ID: <Pine.LNX.4.64.0708141012520.25173@dhalsim.dreamhost.com>
On Sat, 11 Aug 2007, Michael A. Puls II wrote:
> On 8/10/07, Maciej Stachowiak <mjs at apple.com> wrote:
> > I would also suggest calling it something other than hashchange. I
> > realize the term "hash" is used in other places in the HTML DOM to
> > refer to the fragment ID but it sounds weird in an event name like
> > that. CSS uses "target" and the URI RFC uses "fragment identifier".
> 
> I like "hashchange" even if it's not perfectly descriptive.
> 
> However, "fragmentidentifierchange" although long, isn't much longer
> than DOMAttributeModified
> and is shorter than say, DOMNodeRemovedFromDocument.
> 
> addEventListener("fragmentidentifierchange" doesn't seem too bad to me.
> 
> And, if for some reason you wanted it shortened in your script, you
> could just do:
> 
> var hashchange = "fragmentidentifierchange";
> a.addEventListener(hashchange
> b.addEventListener(hashchange
> c.addEventListener(hashchange

I don't know.

   <body onfragmentidentifierchange="">

...seems a bit overly long to me, still.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 14 August 2007 03:15:48 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:36 UTC