W3C home > Mailing lists > Public > www-style@w3.org > February 2014

Re: [shadow-styling] Named parts, styling built-in form controls, and shadow styling (was Re: Goals for Shadow DOM review)

From: Edward O'Connor <eoconnor@apple.com>
Date: Fri, 21 Feb 2014 11:34:40 -0800
To: www-style@w3.org
Message-id: <m2sirc8dkf.fsf@eoconnor.apple.com>
Hi Brian,

You wrote:

> We did have named parts at one time, i think that they turned out to
> have the same "shadow-deep" problem with composibility.

I think the current approach to the shadow-deep problem misses one of
the scenarios that motivates the desire for type 2 encapsulation.

Consider a page that has a component B. It also has a component A that
itself contains a component B.

Page
 |
 |-A
 | |
 | \-B1
 |
 \-B0

There are a couple of different styling scenarios that I think any
acceptable component model should support:

 1. The author of component A has created a small, self-contained widget
    that has its own look-and-feel. When embedded on different pages,
    all A widgets should look the same. It should be really hard for
    page authors embedding component A to screw this up. B1 shouldn't be
    affected by CSS the page author intended to affect B0.

 2. The author of component A has created a widget that should adapt to
    the look-and-feel of the page embedding it. The page author wants to
    style all of the Bs on the page in the same way. B1 should look the
    same as B0.

Now, the page also has a component C that contains a B:

Page
 |
 |-A
 | |
 | \-B1
 |
 |-C
 | |
 | \-B2
 |
 \-B0

Say component A is scenario 1 and component C is scenario 2. The page
author should be able to straightforwardly author CSS that styles B0 and
B2 but not B1.


Ted
Received on Friday, 21 February 2014 19:35:09 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:19 UTC