Open
Bug 906714
(url)
Opened 11 years ago
Updated 1 year ago
[meta] Implement URL parser per URL Standard
Categories
(Core :: Networking, task, P5)
Tracking
()
NEW
People
(Reporter: annevk, Unassigned)
References
(Depends on 30 open bugs, Blocks 3 open bugs, )
Details
(Keywords: meta, Whiteboard: [necko-would-take])
We should replace our current URL parser with the one described by http://url.spec.whatwg.org/ per https://groups.google.com/d/msg/mozilla.dev.platform/V0XjJ-uQbcI/37_DpJzgTbAJ
Tests: https://github.com/annevk/url/ (also has "reference" implementation in JavaScript)
Comment 1•10 years ago
|
||
I think this time we should use something better then strlen, strstr, strchr etc ;)
Adding dep on bug 1024056.
Depends on: 1024056
Reporter | ||
Comment 2•10 years ago
|
||
Just in case someone is working on this, Simon wrote a URL parser in Rust: https://github.com/servo/rust-url/ We plan to change the specification a bit to resemble that structure more as it's a lot nicer: https://www.w3.org/Bugs/Public/show_bug.cgi?id=25946
Alias: url
Depends on: 1225255
Updated•9 years ago
|
Whiteboard: [necko-would-take]
Comment 3•9 years ago
|
||
What is the relationship between this bug and bug 1151899 (use a Rust URL parser)?
If the latter happens soon enough, I'm not sure work on this bug (which is about Gecko implementation?) will be that important.
Comment 4•9 years ago
|
||
(sorry, submitted too quickly).
Said differently, should the focus rather be on making sure the rust url parser is conforming to http://url.spec.whatwg.org/ ?
Comment 5•9 years ago
|
||
(In reply to David Bruant from comment #3)
> What is the relationship between this bug and bug 1151899 (use a Rust URL
> parser)?
> If the latter happens soon enough, I'm not sure work on this bug (which is
> about Gecko implementation?) will be that important.
Bug 1151899 means switching our parsing backend to the one written in Rust.
While the backend is the most important part of conforming to the spec, this bug also covers other issues, such as the DOM APIs and the URL bar in Firefox.
(In reply to David Bruant from comment #4)
> (sorry, submitted too quickly).
> Said differently, should the focus rather be on making sure the rust url
> parser is conforming to http://url.spec.whatwg.org/ ?
The rust parser is doing quite well in conforming to the spec as far as I can tell. Any issues that are found will definitely be fixed.
Updated•8 years ago
|
Reporter | ||
Updated•8 years ago
|
Depends on: url-oxidation
Comment 6•7 years ago
|
||
We already seem to have the web-dev-facing bits of this spec documented, but I'm still adding dev-doc-needed just in case.
Keywords: dev-doc-needed
Comment 7•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
Updated•6 years ago
|
Keywords: dev-doc-needed
Updated•6 years ago
|
Type: defect → task
Comment 10•4 years ago
|
||
Hear, hear! Traction after 22 years :-)
Thank you for looking into it.
Depends on: 32442
Updated•4 years ago
|
a11y-review: requested → ---
status-firefox86:
affected → ---
status-firefox87:
affected → ---
status-firefox88:
fixed → ---
relnote-firefox:
? → ---
Updated•3 years ago
|
Keywords: meta
Summary: Implement URL parser per URL Standard → [meta] Implement URL parser per URL Standard
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Updated•2 years ago
|
Blocks: interop-2023
Comment 12•2 years ago
|
||
Updated•2 years ago
|
Blocks: interop-2023-url
Updated•2 years ago
|
No longer blocks: interop-2023
Updated•2 years ago
|
No longer blocks: interop-2023-url
Depends on: interop-2023-url
Comment 13•1 year ago
|
||
Anticipated fallout of aligning with the URL standard for allowing data:
URLs to be base URLs:
You need to log in
before you can comment on or make changes to this bug.
Description
•