Improve definition of URL for Documents created by DOMParser #46
Assignees
Labels
Comments
|
Tests: web-platform-tests/wpt#15548 |
domenic
added a commit
to whatwg/html
that referenced
this issue
Jan 4, 2020
This moves the DOMParser class from https://w3c.github.io/DOM-Parsing/ into HTML, per various offline discussions. Along the way, it improves the spec in several minor ways and a couple notable ways: * It precisely defines the URL of the resulting document, in a way that matches the majority of browsers. As such, this closes w3c/DOM-Parsing#46. * It more clearly states how the parser error documents are created, namely that they also get their content type and URL set.
3 tasks
|
This is being done in whatwg/html#5190 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The spec currently refers to the "active document", which is a property of a browsing context. However, it doesn't define which browsing context it's getting the "active document" from.
However, this doesn't appear to be the correct concept in the first place. Gecko, Chrome and WebKit all seem to use the URL of the relevant global's associated Document.
In particular, this difference is significant if the browsing context is navigated. In that case, the "active document" would change, and the spec would suggest using the URL the BC was navigated to. All browsers I tested use the pre-navigation URL instead.
The text was updated successfully, but these errors were encountered: