yuzh...@chromium.org https://github.com/whatwg/dom/issues/478 Specification: https://dom.spec.whatwg.org/#dom-parentnode-replacechildren TAG review is not needed; this is a new API that mainly uses existing APIs, node.removeChild and node.appendChild, to implement its behavior. This API, when invoked, replaces all children of the ParentNode with argument nodes passed-in.
Risks
This should be fully debuggable. Yes Yes https://wpt.fyi/results/dom?label=master&label=experimental&aligned&q=parentnode-replacechildren.html https://chromestatus.com/feature/6143552666992640
Specification: https://dom.spec.whatwg.org/#dom-parentnode-replacechildren TAG review is not needed; this is a new API that mainly uses existing APIs, node.removeChild and node.appendChild, to implement its behavior.
This API, when invoked, replaces all children of the ParentNode with argument nodes passed-in.
Risks
There's no interoperability and compatibility risk as both Safari and Firefox have shipped their implementation.
Firefox: Shipped (https://bugzilla.mozilla.org/show_bug.cgi?id=1626015)Edge: No public signals Safari: Shipped (https://bugs.webkit.org/show_bug.cgi?id=198578) Web developers: No signals This API makes web developers more efficient. They can replace a node's children with other nodes via one API. N/A N/AThis should be fully debuggable. Yes Yes https://wpt.fyi/results/dom?label=master&label=experimental&aligned&q=parentnode-replacechildren.html https://chromestatus.com/feature/6143552666992640
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABgHHk6ANixYo_Ee-JotHqmngKpS%3DkxPQo8yuk11BKSvzDko_w%40mail.gmail.com.
yuzh...@chromium.org https://github.com/whatwg/dom/issues/478 Specification: https://dom.spec.whatwg.org/#dom-parentnode-replacechildren TAG review is not needed; this is a new API that mainly uses existing APIs, node.removeChild and node.appendChild, to implement its behavior. This API, when invoked, replaces all children of the ParentNode with argument nodes passed-in.
Risks
There's no interoperability and compatibility risk as both Safari and Firefox have shipped their implementation.
Firefox: Shipped (https://bugzilla.mozilla.org/show_bug.cgi?id=1626015)Edge: No public signals Safari: Shipped (https://bugs.webkit.org/show_bug.cgi?id=198578) Web developers: No signals This API makes web developers more efficient. They can replace a node's children with other nodes via one API. N/A N/AThis should be fully debuggable. Yes Yes https://wpt.fyi/results/dom?label=master&label=experimental&aligned&q=parentnode-replacechildren.html https://chromestatus.com/feature/6143552666992640
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABgHHk6ANixYo_Ee-JotHqmngKpS%3DkxPQo8yuk11BKSvzDko_w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqHyfWKFqSKyf61WqZ0eZBVCQ2_j400wqVOWi-q3QgHvRg%40mail.gmail.com.
Thanks everyone for reviewing.Yoav,
>>> That's not an explainer. It would be good to outline what is planned to ship here, what use cases it covers, how developers are supposed to use it, etc.
I've added a quick explainer, https://github.com/yuzhe-han/ParentNode-replaceChildren, which goes more in details on the API being shipped, its usage with example, and a polyfill for unsupported browsers.
I've updated the chromestatus page accordingly.
>>> The internal implementation details don't seem highly relevant here. What matters is the API shape. If it's a simple API, then the review should be brief.
I think a TAG review doesn't seem necessary. It's a minor feature and Firefox and Safari already shipped it. However, if you feel strongly about it, I'll create a TAG review.
>>> What are web developers expected to do? Polyfill this API for browsers which don't support it?
I provided an example, along with a polyfill, in the explainer.
Thanks,Han