W3C home > Mailing lists > Public > public-html-wg-issue-tracking@w3.org > April 2010

ISSUE-113 (forced-fragment): add a preventable forced-fragment method [HTML 5 spec]

From: HTML Weekly Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 28 Apr 2010 21:37:45 +0000 (GMT)
To: public-html-wg-issue-tracking@w3.org
Message-Id: <20100428213745.A29D25F76D@stu.w3.org>

ISSUE-113 (forced-fragment): add a preventable forced-fragment method [HTML 5 spec]

http://www.w3.org/html/wg/tracker/issues/113

Raised by: Maciej Stachowiak
On product: HTML 5 spec

Escalated from: http://www.w3.org/Bugs/Public/show_bug.cgi?id=6610
Requested by: Nick Levinson

A URL with a special fragment identifier should take a user to the fragment
another user intends even if the page author didn't intend it.

Thus, when a search engine shows me a snippet, I should be able to go directly
to that snippet, a problem with some long documents. Using the find function on
a page isn't always feasible.

A page author should be able to disable the action of all such URLs by ignoring
the special fragment identifier and taking the user to the top of the page.

I'm not sure if additional syntax for URLs needs to be defined or if the
standard "#" fragment identifier can serve by having HTML5 recognize it even if
the page author did not explicitly define an anchor for the fragment.
Received on Wednesday, 28 April 2010 21:37:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:48:29 UTC