This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7799 - If the fragid doesn't match an ID or a name in the document, then surely the browser should revert to doing a text search for the fragid text in the document
Summary: If the fragid doesn't match an ID or a name in the document, then surely the ...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: NE
Depends on:
Blocks:
 
Reported: 2009-10-04 00:00 UTC by contributor
Modified: 2010-10-04 14:31 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2009-10-04 00:00:46 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#scroll-to-fragid

Comment:
If the fragid doesn't match an ID or a name in the document, then surely the browser should revert to doing a text search for the fragid text in the document

Posted from: 80.5.223.97
Comment 1 Simon Pieters 2009-10-05 11:26:06 UTC 
Why should the browser do that? I think no current browser does that, and I wouldn't be surprised if pages rely on setting fragid to something without it having side-effects as is suggested here.