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

Re: Shadow tree style isolation primitive

From: Brian Kardell <bkardell@gmail.com>
Date: Tue, 13 Jan 2015 20:11:42 -0500
Message-ID: <CADC=+jcbifYTctOHHUW8fm0Lkxeh7K=biVbcZG5U7dTQozN3KQ@mail.gmail.com>
To: Ryosuke Niwa <rniwa@apple.com>
Cc: Chaals from Yandex <chaals@yandex-team.ru>, Anne van Kesteren <annevk@annevk.nl>, "www-style@w3.org" <www-style@w3.org>, WebApps WG <public-webapps@w3.org>
On Tue, Jan 13, 2015 at 8:09 PM, Ryosuke Niwa <rniwa@apple.com> wrote:

>
> On Jan 13, 2015, at 3:46 PM, Brian Kardell <bkardell@gmail.com> wrote:
>
>
>
> On Tue, Jan 13, 2015 at 2:07 PM, Ryosuke Niwa <rniwa@apple.com> wrote:
>
> To separate presentational information (CSS) from the semantics (HTML).
>> Defining both style isolation boundaries and the associated CSS rules in an
>> external CSS file will allow authors to change both of them without having
>> to modify every HTML documents that includes the CSS file.  Of course, this
>> is a non-starter for Web apps that require a lot of scripting, but style
>> isolation is a very useful feature for a lot of static pages as well.
>>
>> - R. Niwa
>>
>>
> Ryosuke,
>
> Should you also be able to do this from JavaScript/DOM in your opinion?
> Like, forget shadow dom as it is today in chrome or proposed -- should you
> be able to do something like
>
> ```
>     element.isolateTree = true;
> ```
>
> and achieve a similar effect?  If not, why specifically?
>
>
> Or element.setAttribute('isolatetree', true);  I can't think of a reason
> not to do this.
>
> - R. Niwa
>
>
So if that is a given, why can we not start there and explain how it would
work and use it to fashion increasingly high abstractions - hopefully with
the ability to do some experimentation outside of native implementations?


-- 
Brian Kardell :: @briankardell :: hitchjs.com
Received on Wednesday, 14 January 2015 01:12:14 UTC

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