W3C home > Mailing lists > Public > public-html@w3.org > March 2010

[Bug 6610] add a preventable forced-fragment method

From: <bugzilla@wiggum.w3.org>
Date: Sun, 28 Mar 2010 19:39:46 +0000
To: public-html@w3.org
Message-Id: <E1NvyKo-0005pz-Hg@wiggum.w3.org>

Nick Levinson <Nick_Levinson@yahoo.com> changed:

           What    |Removed                     |Added
             Status|VERIFIED                    |REOPENED
           Keywords|                            |TrackerRequest
         Resolution|NEEDSINFO                   |

--- Comment #6 from Nick Levinson <Nick_Levinson@yahoo.com>  2010-03-28 19:39:46 ---
This would help users find more content and find it faster, even when a page
author has not created a fragment. I'm requesting escalation.

This bug is already assigned, so I don't know if its status is correct..

Suggested title: add a preventable forced-fragment method

Suggested text:

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.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Sunday, 28 March 2010 19:39:47 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:14 UTC