W3C home > Mailing lists > Public > www-style@w3.org > January 2012

Re: [css3-regions] @region and specificity

From: Vincent Hardy <vhardy@adobe.com>
Date: Thu, 26 Jan 2012 17:28:12 -0800
To: Alex Mogilevsky <alexmog@microsoft.com>
CC: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org list" <www-style@w3.org>
Message-ID: <0F20B7B9-BDE9-4D5F-9089-5E2174D885C1@adobe.com>

Christoph has proposed an alternate syntax:

 h1:region(first) { color: purple; }
 h1 { color: blue; }

I tend to agree with Alex. I think regions decouple the content from their layout containers so that, typically, we will have a different chain of containers apply depending on the orientation, the device width/height or other factors like this.

@fantasai: is what Christoph proposed what you had in mind?


On Jan 5, 2012, at 11:21 PM, Alex Mogilevsky wrote:

 From: fantasai [mailto:fantasai.lists@inkedblade.net]
 Sent: Monday, December 26, 2011 7:56 PM

 The structure and usage of a design's region-specific styling is very similar to the
 structure and usage of contextual styling (using descendant selectors), and not
 similar to the structure and useage of media-specific styling. Given that, I'm uneasy
 with using @media as an analogy here and discarding the specificity of the region.

I am not sure what you are proposing here. The way it is defined now, it does manage to avoid interfering with specificity. Earlier proposals were way harder to define and had complicated interaction with other selectors.

Analogy with @media is also reasonable IMO. It makes sense to me that styles specific to page size and styles specific to page number work the same way. Why not?

Do you have something else in mind that you like more?

Received on Friday, 27 January 2012 01:28:42 UTC

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