W3C home > Mailing lists > Public > www-style@w3.org > March 2011

Re: [CSS Regions] Update available

From: Brady Duga <duga@ljug.com>
Date: Fri, 25 Mar 2011 13:55:41 -0700
Cc: "www-style@w3.org" <www-style@w3.org>
Message-Id: <94448D22-5269-46DD-BBB9-98510795AC4A@ljug.com>
To: Arno Gourdol <agourdol@adobe.com>
Hi Arno,

Glad to see that this is progressing! I just started to read through it and am a little confused about the selector matching in the Description section. It's quite possible I'm just being dim, but it seems like this:

"If the CSS selector has no matching element, the rule will be ignored until a matching element becomes available."

is really just saying "if the selector doesn't match anything then the selector doesn't match anything until the selector matches something." Isn't this just standard selector behavior? Then this sentence really confuses me:

"If no CSS selector is specified in the ::slot() rule, the element will be created as a root element."

How can you have a pseudo-element without a selector? Do you mean if you just have this:

::slot() { ... }

If so, isn't that redefining the basic selector mechanism? I would think that is just shorthand for:

*::slot() { ... }

since the '*' is optional when the universal selector is immediately followed by a pseudo-element. 


On Mar 25, 2011, at 12:49 PM, Arno Gourdol wrote:

> We have an update of our CSS Regions proposal. You can find it here:
> http://dev.w3.org/csswg/css3-regions/
> First, apologies for the unprocessed document. This will be resolved promptly. In the meantime, please click Overview.src.html in directory above to get to the document.
> This version incorporates some of the feedback we've received at the F2F meeting and on this mailing list. Thanks to everyone for your suggestions and comments.
> The document has been broken up in three major sections: slots (which describe a way of creating elements using CSS declarations and could be used for regions and other purposes), regions (which are a way of implementing story threading) and exclusions (to specify areas to be avoided for the purpose of text layout).
> We would be very interested in feedback regarding the structure of the document, and whether these proposals should remain in one document, be merged with other proposals, or separated in multiple documents.
> We also look forward to feedback regarding the new proposed syntax.
> – Arno  ❉  @arnog  ❉  Director of Engineering, Runtime Foundation
Received on Friday, 25 March 2011 20:56:20 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:44 UTC