W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: Imperative API for Node Distribution in Shadow DOM (Revisited)

From: Hayato Ito <hayato@chromium.org>
Date: Sat, 25 Apr 2015 17:00:46 +0000
Message-ID: <CAFpjS_39wsHOd47jDVSVFQx3YQZShG6SSiFzCdidwm7d1j_Wpw@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>, Ryosuke Niwa <rniwa@apple.com>
Cc: WebApps WG <public-webapps@w3.org>, Erik Bryn <erik@erikbryn.com>, Dimitri Glazkov <dglazkov@google.com>
Thank you, guys.
I really appreciate if you guys could use the W3C bug, 18429, to discuss
this kind of specific topic about Shadow DOM so that we can track the
progress easily in one place. I'm not fan of the discussion being scattered.


On Sat, Apr 25, 2015 at 9:32 AM Anne van Kesteren <annevk@annevk.nl> wrote:

> On Sat, Apr 25, 2015 at 12:17 AM, Ryosuke Niwa <rniwa@apple.com> wrote:
> > In today's F2F, I've got an action item to come up with a concrete
> workable
> > proposal for imperative API.  I had a great chat about this afterwards
> with
> > various people who attended F2F and here's a summary.  I'll continue to
> work
> > with Dimitri & Erik to work out details in the coming months (our
> deadline
> > is July 13th).
> >
> > https://gist.github.com/rniwa/2f14588926e1a11c65d3
> I thought we came up with something somewhat simpler that didn't
> require adding an event or adding remove() for that matter:
>   https://gist.github.com/annevk/e9e61801fcfb251389ef
> I added an example there that shows how you could implement <content
> select>, it's rather trivial with the matches() API. I think you can
> derive any other use case easily from that example, though I'm willing
> to help guide people through others if it is unclear. I guess we might
> still want positional insertion as a convenience though the above
> seems to be all you need primitive-wise.
> --
> https://annevankesteren.nl/
Received on Saturday, 25 April 2015 17:01:15 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC