[whatwg] hashchange only dispatched in history traversal

Křištof Želechovski giecrilj at stegny.2a.pl
Mon Aug 13 09:17:21 PDT 2007

A fragment identifier was rather like a bookmark because you cannot have a
big fragment inside an anchor because a big fragment is a block-level
element and an anchor would not like having a block-level element inside.
On the other hand, the path of the URL refers to the whole document, not
just to the beginning of the document.  That is the difference between a
fragment and a bookmark.  A fragment has the beginning and the end; a
bookmark does not have the end or, if you prefer, it is like an empty
fragment where the end is equal to the beginning (it is in the same
block-level element).

-----Original Message-----
From: Maciej Stachowiak [mailto:mjs at apple.com] 
Sent: Sunday, August 12, 2007 11:59 PM
To: Krzysztof Żelechowski
Cc: 'Ian Hickson'; 'WHATWG'
Subject: Re: [whatwg] hashchange only dispatched in history traversal

On Aug 12, 2007, at 10:38 AM, Krzysztof Żelechowski wrote:

> Dnia sobota, 11 sierpnia 2007 22:14, Maciej Stachowiak napisał:
>> On Aug 11, 2007, at 10:00 AM, Křištof Želechovski wrote:
>>> Originally the name after the hash was a bookmark, not a fragment,
>>> because
>>> it would be defined on an anchor.  I agree that until the new
>>> semantic makes
>>> it to the common knowledge using the name "fragment" for the purpose
>>> may be
>>> surprising for some developers.
>> When was it called a bookmark? I'm pretty sure it has been called a
>> fragment identifier back to at least the late '90s.
> In the early '90s?  And I did not say it was called a bookmark but  
> it was like
> a bookmark semantically.

Apparently it's been called a fragment identifier for about as long as  
the World Wide Web has existed. I don't know what you mean by "like a  
bookmark semantically". It's no more or less like a bookmark than any  
other part of a URI.


More information about the whatwg mailing list