Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It should be noted that parseFromString can throw exceptions #51

Closed
bbarker opened this issue Apr 18, 2019 · 1 comment · Fixed by whatwg/html#5190
Closed

It should be noted that parseFromString can throw exceptions #51

bbarker opened this issue Apr 18, 2019 · 1 comment · Fixed by whatwg/html#5190
Assignees

Comments

@bbarker
Copy link

bbarker commented Apr 18, 2019

This should probably be obvious, but it is not stated per usual, as far as I can tell, at https://www.w3.org/TR/DOM-Parsing/#the-domparser-interface

@domenic domenic self-assigned this Jan 4, 2020
@domenic
Copy link
Collaborator

domenic commented Jan 4, 2020

I've added this in whatwg/html#5190

domenic added a commit to whatwg/html that referenced this issue Jan 28, 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.

This also closes w3c/DOM-Parsing#51 and
w3c/DOM-Parsing#34 by adding explanatory
notes for points that confused people enough to file an issue.

Tests: web-platform-tests/wpt#21041
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants