Sounds like this may cause WebCompatibility issues? How worried are we about this? Can we mitigate this through testing?
Regards, Florin. -----Original Message----- From: dev-platform [mailto:dev-platform-bounces+florin.mezei=softvisioninc...@lists.mozilla.org ] On Behalf Of smaug Sent: Monday, April 18, 2016 8:30 PM To: dev-platform@lists.mozilla.org Subject: Re: Intent to ship: ParentNode.prepend(), ParentNode.append(), ChildNode.before(), ChildNode.after(), ChildNode.replaceWith() OK from me. Need to still carefully look for any possible regressions. -Olli On 04/18/2016 08:11 PM, Jocelyn Liu wrote: > As of Firefox 48 I intend to ship ParentNode.prepend(), > ParentNode.append(), ChildNode.before(), ChildNode.after(), and > ChildNode.replaceWith() on all platforms. > These methods would enable web developers to insert a set of nodes or > strings into a parent node's children list or before/after a child > node, or replace a node with them. > > Implementation bug: > https://bugzilla.mozilla.org/show_bug.cgi?id=911477 > Link to standard: > https://dom.spec.whatwg.org/#parentnode > https://dom.spec.whatwg.org/#childnode > > Enabled in WebKit nightly, except for Safari. > Blink issue: > https://bugs.chromium.org/p/chromium/issues/detail?id=255482, > changesets were backed out, haven't been relanded yet. > > Regards, > Jocelyn > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform