Thanks
As per Philip's suggestion, We are implementing new DOM convenience APIs i.e. ChildNode.before((Node or DOMString)... nodes) ChildNode.after((Node or DOMString)... nodes) ChildNode.replaceWith((Node or DOMString)... nodes) ParentNode.prepend((Node or DOMString)... nodes) ParentNode.append((Node or DOMString)... nodes)
in a group, with a RunTime Flag.
As Unscopeable is supported, we will use Unscopeable for all these apis.
-Paritosh
The missing bindings are there now. https://code.google.com/p/chromium/issues/detail?id=462916On Wednesday, April 15, 2015 at 9:59:18 AM UTC+2, Philip Jägenstedt wrote: Dimitri pointed out that ES6 Unscopeables are already supported:
https://www.chromestatus.com/features/4543115071324160
That means that only the bindings bit is missing:
https://code.google.com/p/chromium/issues/detail?id=462916
Philip
On Tue, Apr 14, 2015 at 8:10 PM, Philip Jägenstedt <phi...@opera.com> wrote:
> Hi Paritosh,
>
> We discussed this in today's API owners meeting and have some feedback.
>
> First, ChildNode.before((Node or DOMString)... nodes) is one in a
> group of new DOM convenience APIs that would make sense to implement
> as a group, the others being:
> ChildNode.after((Node or DOMString)... nodes)
> ChildNode.replaceWith((Node or DOMString)... nodes)
> ParentNode.prepend((Node or DOMString)... nodes)
> ParentNode.append((Node or DOMString)... nodes)
>
> All of these have [Unscopeable] in the IDL and since support for that
> seems to be on the near horizon it seems safest to wait for a little
> bit. If it turns out that [Unscopeable] isn't going to be done any
> time soon we'll have to re-evaluate. (ChildNode.remove() is already
> shipping without [Unscopeable].)
>
> So in summary, LGTM to implement
> ChildNode.before()/after()/replaceWith() and
> ParentNode.prepend()/append().
>
> Before shipping, we'd like to run this through TAG review, as a fairly
> simple test of that whole process. Alex is preparing a template to
> request that review.
>
> Philip
>
> On Tue, Apr 14, 2015 at 2:35 PM, Paritosh Kumar <parit...@samsung.com> wrote:
>> Contact emails
>>
>> parit...@samsung.com
>>
>>
>> Spec
>>
>> https://dom.spec.whatwg.org/#dom-childnode-before
>>
>>
>> Summary
>>
>> Add ChildNode.before() API.
>>
>>
>> Motivation
>>
>> This will allow a web developer to insert a set of Node or DOMString objects
>> in the children list of this ChildNode's parent, just before this ChildNode.
>> DOMString objects are inserted as equivalent Text nodes. We can use
>> Node.insertBefore() but it can be used for single node only. No direct way
>> for
>>
>> inserting a set of children.
>>
>>
>> Compatibility Risk
>>
>> Low, As other browsers are also implementing it.
>>
>>
>>
>>
>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>> Linux, Chrome OS, Android, and Android WebView)?
>>
>> Yes.
>>
>>
>> OWP launch tracking bug?
>>
>> None.
>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to blink-dev+...@chromium.org.
|