ParentNode.replaceChildren is excluded, but it's not clear to me why
See original GitHub issueIt appears that the method replaceChildren
on the interface ParentNode
has explicitly been excluded. It’s not clear to me why this is; as far as I can tell it’s stable and present in most browsers. This change was introduced in a seemingly unrelated pull-request, which doesn’t provide any hints as to why this was done. Is there a reason for this? Was this an accident?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Element.replaceChildren() - Web APIs - MDN Web Docs
The Element.replaceChildren() method replaces the existing children of a Node with a specified new set of children.
Read more >DOM replaceChild not replacing all specified elements
DOM replaceChild not replacing all specified elements ... I cannot for the life of me figure out why all of the region tags...
Read more >ParentNode.replaceChildren() Method - Chrome Platform Status
Loop through node's children and call node.removeChild() on each one. Then call node.append(nodes). This replaceChildren API enables web ...
Read more >1. Getting Started - Greasemonkey Hacks [Book] - O'Reilly
The first thing you need to do to get started with Greasemonkey is install it. Open Firefox and go to http://greasemonkey.mozdev.org.
Read more >DrexelMed Annotated Video - WebCampus - Drexel University
removeChild(Y)}else{setTimeout(arguments.callee,10)}})()}else{Y.parentNode.replaceChild(g(Y),Y)}}function g(ab){var aa=C("div");if(M.win&&M.ie){aa.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It wasn’t widely available back in 2020. We can now remove the exclusion.
Closing because @saschanaz is one of the code-owners of this repository.