W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

Re: Shadow tree style isolation primitive

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 5 Feb 2015 14:26:22 +0100
Message-ID: <CADnb78hEv6iMQc+GxJVnPZVWd7SMrmk=ENAbWz1_MfmC+G7BxA@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Olli Pettay <olli@pettay.fi>, Brian Kardell <bkardell@gmail.com>, Dimitri Glazkov <dglazkov@google.com>, "www-style@w3.org" <www-style@w3.org>, WebApps WG <public-webapps@w3.org>
On Thu, Feb 5, 2015 at 1:37 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> By your statements implying that composition issues can just be
> handled by better discipline and some selector modification, in the
> message I responded to earlier.  I'm not sure how to interpret those
> statement if you didn't mean that composition wasn't worth solving.

I think Olli already clarified that he is happy to solve that use
case, but that it's unclear that the complexity of shadow DOM is
warranted.

Note though that e.g. React is out there solving this without need for
shadow DOM. Ember is out there and cannot use shadow DOM due to its
coupling of style isolation primitives with event retargeting and
therefore also has its own solution. (And last I heard seems to take
inspiration from React.) Talking to the developers working on these
frameworks it's pretty clear we haven't exactly nailed it here and
that it's worth exploring what can be done instead.


-- 
https://annevankesteren.nl/
Received on Thursday, 5 February 2015 13:26:48 UTC

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