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

Re: [Shadow DOM] Shadown DOM and Regions CSSOM

From: Dominic Cooney <dominicc@google.com>
Date: Fri, 22 Jun 2012 14:52:06 +0900
Message-ID: <CAHnmYQ8018=f7+aay9KJchNFTJBSTvpsrQnBPE7+4wpB4J=fiA@mail.gmail.com>
To: Andrei Bucur <abucur@adobe.com>
Cc: WebApps WG <public-webapps@w3.org>, "dglazkov@chromium.org" <dglazkov@chromium.org>
On Thu, Jun 21, 2012 at 6:23 PM, Andrei Bucur <abucur@adobe.com> wrote:

> Hello,
>
> This is a cross-post from the www-style discussion list in case anyone is
> interested about this subject:
>
> Currently the CSS Regions spec doesn't mention what happens with regions
> that are part of a shadow tree. The NamedFlow interface exposes the
> getRegions API that "returns the sequence of regions in the region chain
> associated with the named flow". I suppose the CSSOM needs to be adapted
> to take into account the shadow boundaries.
>
> One way to do it is to add NamedFlow accessor APIs to the shadow root
> object, similar to what's available on the Document. The NamedFlow objects
> returned using the new API will provide access to the regions found in the
> shadow tree. The NamedFlow objects returned from the host document give
> access only to the regions above the shadow boundary.
>
> Thoughts?


That makes sense to me. It is in line with the Shadow DOM concept of
upper-boundary encapsulation and is analogous to the methods and properties
on ShadowRoot, like NodeSelector, that provide access to the encapsulated
stuff.

Dominic
Received on Friday, 22 June 2012 05:52:35 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT