Closed
Bug 1497557
Opened 6 years ago
Closed 3 years ago
<a> "protocol" shows as "http:" for data-relative paths, instead of ":"
Categories
(Core :: DOM: Core & HTML, enhancement, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
88 Branch
People
(Reporter: loganfsmyth, Assigned: valentin)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
If you load a data: URL on Firefox with a link on it, the `protocol` of the <a> is supposed to be ":" (because it's an unparseable URL), but Firefox appears to returning "http:" or "https:" for the protocol. For example, if you load this and look at the console: data:text/html,<script>console.log(document.createElement('a').protocol); </script> this will log "http:".
Updated•6 years ago
|
Priority: -- → P2
Comment 2•3 years ago
|
||
The spec definition:
https://html.spec.whatwg.org/multipage/links.html#dom-hyperlink-protocol
Assignee | ||
Comment 3•3 years ago
|
||
Thank for the pointer. I think it's an easy enough fix.
Assignee: nobody → valentin.gosu
Severity: normal → S3
Whiteboard: [necko-triaged]
Assignee | ||
Comment 4•3 years ago
|
||
Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/af234fcd4e15 <a> "protocol" should be ":" for data-relative paths, instead of "http:" r=baku
Comment 6•3 years ago
|
||
Backed out for causing failureS at a-element-xhtml.xhtml.
Backout link: https://hg.mozilla.org/integration/autoland/rev/ae6f802e9ca8bc638659d53445761330cb231733
Failure log: https://treeherder.mozilla.org/logviewer?job_id=331577133&repo=autoland&lineNumber=6797
Flags: needinfo?(valentin.gosu)
Assignee | ||
Updated•3 years ago
|
Flags: needinfo?(valentin.gosu)
Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/f529f4e42e7e <a> "protocol" should be ":" for data-relative paths, instead of "http:" r=baku
Comment 8•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox88:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
Updated•3 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•