Closed Bug 662184 Opened 14 years ago Closed 14 years ago

Fragment identifier not implemented correctly "for" data uris

Categories

(Core :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: emil.langrock, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0) Gecko/20110310 Firefox/4.0 Iceweasel/4.0 Build Identifier: First thing: I know about #243917 and the bugs which marked there as duplicate. The problem is that the argumentation is wrong. Here the interesting comment which was completely ignored till now: Per RFC 3986, Fragment ID should work regardless of the scheme. http://tools.ietf.org/html/rfc3986#section-3.5 > Fragment identifier semantics are independent of the > URI scheme and thus cannot be redefined by scheme specifications. See also: http://www.ietf.org/mail-archive/web/uri-review/current/msg00931.html So it is wrong to argument with "data: is not an nsIURL in Mozilla". This is maybe a show blocker in the current implementation, but not a reason that it should not be fixed. Reproducible: Always
This has been changed for Firefox 6.0a2 by bug 308590 and bug 658949. data:text/html,<style type="text/css"> h1:target {color:red}</style><h1 id="a">A</h1><h1 id="b">B</h1>#b WFM Mozilla/5.0 (Windows NT 5.0; rv:7.0a1) Gecko/20110605 Firefox/7.0a1 [bug 243917 comment #10 is no longer correct as the fragment is now available to an nsIURI] Marking WORKSFORME as it is not clear which to mark as duplicate.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.