Re: [csswg-drafts] [css-cascade] Probably css-cascade shouldn't say that there's a specified value for every property and element.

Fundamentally, CSS has an abstract concept of a document tree which is given as input to CSS. Shadow DOM has decided to compose the flat tree and give it to CSS for presentation. You can give it other kinds of trees, it doesn't have to be a DOM tree.

Where and how best to define the interaction of CSS and Shadow DOM--the fact that DOM hands over the flat tree, and not some other construct, for CSS to style--isn't entirely clear to me... In a sense, it's the DOM's semantics that says "this is what should be presented to the user", so I could make a pretty good argument that the DOM should be the one defining that we use the flat tree. (If we used a different tree technology, there wouldn't be a “flat tree” definition to use, but if DOM was presented with some other style sheet technology, it would still need to define that it's the flat tree that gets presented.) But in any case, we'll probably want to gather all of these issues and solve them together, as clearly the current situation is a bit incoherent.

-- 
GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2562#issuecomment-413772975 using your GitHub account

Received on Friday, 17 August 2018 06:41:16 UTC