ISSUE-113: add a preventable forced-fragment method

forced-fragment

add a preventable forced-fragment method

State:
CLOSED
Product:
HTML 5 spec
Raised by:
Maciej Stachowiak
Opened on:
2010-04-28
Description:
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.
Related Actions Items:
No related actions
Related emails:
  1. Re: ISSUE-113 (forced-fragment): Chairs Solicit Proposals (from rubys@intertwingly.net on 2010-06-03)
  2. [minutes] HTML WG 20100603 (from plh@w3.org on 2010-06-03)
  3. {agenda} HTML WG telecon 2010-06-03 (from rubys@intertwingly.net on 2010-06-02)
  4. RE: {agenda} HTML WG telecon 2010-05-27 (from adrianba@microsoft.com on 2010-05-27)
  5. Re: {agenda} HTML WG telecon 2010-05-27 (from faulkner.steve@gmail.com on 2010-05-27)
  6. Re: {agenda} HTML WG telecon 2010-05-27 (from laura.lee.carlson@gmail.com on 2010-05-27)
  7. {agenda} HTML WG telecon 2010-05-27 (from rubys@intertwingly.net on 2010-05-26)
  8. {agenda} HTML WG telecon 2010-05-20: Surveys close, Publishing new Working Drafts (from mjs@apple.com on 2010-05-19)
  9. [Bug 6610] add a preventable forced-fragment method (from bugzilla@jessica.w3.org on 2010-05-12)
  10. RE: {agenda} HTML WG telcon 2010-04-29: Action items, new issues, Task Force reports - minutes of the meeting (from adrianba@microsoft.com on 2010-04-29)
  11. ISSUE-113 (forced-fragment): Chairs Solicit Proposals (from mjs@apple.com on 2010-04-28)
  12. {agenda} HTML WG telcon 2010-04-29: Action items, new issues, Task Force reports (from mjs@apple.com on 2010-04-28)
  13. ISSUE-113 (forced-fragment): add a preventable forced-fragment method [HTML 5 spec] (from sysbot+tracker@w3.org on 2010-04-28)

Related notes:

Closed without prejudice: http://lists.w3.org/Archives/Public/public-html/2010Jun/0055.html

Sam Ruby, 3 Jun 2010, 17:16:45

Changelog:

Created issue 'add a preventable forced-fragment method' nickname forced-fragment owned by Maciej Stachowiak on product HTML 5 spec, description '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.
' non-public

Maciej Stachowiak, 28 Apr 2010, 21:37:45

Status changed to 'closed'

Sam Ruby, 3 Jun 2010, 17:16:45


Paul Cotton <Paul.Cotton@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Sam Ruby <rubys@intertwingly.net>, Chairs, Michael[tm] Smith <mike@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $