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: Mon, 12 Jan 2015 17:51:26 +0100
Message-ID: <CADnb78j8QOnM-2E_NTmq2U6qQeGrCPxdTFNXRxt5OBFE+8gbqQ@mail.gmail.com>
To: Brian Kardell <bkardell@gmail.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Dimitri Glazkov <dglazkov@google.com>, "www-style@w3.org" <www-style@w3.org>, WebApps WG <public-webapps@w3.org>, Tab Atkins <tabatkins@google.com>
On Mon, Jan 12, 2015 at 5:47 PM, Brian Kardell <bkardell@gmail.com> wrote:
> Controlling it through CSS definitely seems to be very high-level.  To me at
> least it feels like it requires a lot more answering of "how" since it deals
> with identifying elements by way of rules/selection in order to
> differentially identify other elements by way of rules/selection.  At the
> end of the day you have to identify particular elements as different somehow
> and explain how that would work.  It seems better to start there at a
> reasonably low level and just keep in mind that it might be a future aim to
> move control of this sort of thing fully to CSS.

I'm not sure I agree. Unless you make all of CSS imperative it seems
really hard to judge what belongs where.

> Since CSS matching kind of
> conceptually happens on 'not exactly the DOM tree' (pseudo elements, for
> example) it seems kind of similar to me and it might be worth figuring that
> out before attempting another high-level feature which could make answering
> 'what's the path up' all that much harder.

This is false. Selector matching happens against the DOM tree.

Received on Monday, 12 January 2015 16:51:54 UTC

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