-
Notifications
You must be signed in to change notification settings - Fork 299
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
Define ParentNode#replaceChildren #851
Conversation
Thanks @saschanaz! This change looks good to me. Support: I think Firefox and Safari can be considered to be supportive. @mfreed7 thoughts for Chrome? |
@domenic @TimothyGu any interest in writing a jsdom implementation? I wonder if we should start "soft" requiring that for additions to the DOM Standard to add another layer of certainty with regards to the algorithms. |
Sounds like a reasonable proposal to me. I've created a Chromium bug: https://crbug.com/1067384 I honestly don't know how we go about establishing "official support" from Chromium, but I'm at least personally supportive. The use case seems clear and the implementation sounds straightforward. |
FYI, Chromium plans to try to get this implemented in Q2. |
b38a543
to
4a6493b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, the spec already has nice helper algorithms for this.
Thanks @saschanaz for writing all the tests and the change to the DOM Standard and Olli for reviewing! Great work. |
Fixes #478
Closes #755, closes #835.
Tests: web-platform-tests/wpt#22524
Implementation bugs:
Preview | Diff