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

Re: [css3-cascade] Editorial issues.

From: fantasai <fantasai.lists@inkedblade.net>
Date: Mon, 17 Dec 2012 02:11:31 -0800
Message-ID: <50CEEFD3.5060902@inkedblade.net>
To: www-style@w3.org
On 12/14/2012 06:08 AM, Simon Sapin wrote:
> Hi,
> Here are the issues I found or details I was not comfortable with when going through ED-css3-cascade-20121213.
> Section 2 says:
>> So that user agents can avoid retrieving resources for unsupported
>> media types, authors may specify media-dependent ‘@import’ rules.
>> These conditional imports specify comma-separated “media queries”
>> after the URI.
> This sentence suggests that media queries in @import are merely a hint for performance. The section should say that the
> imported stylesheet *must not* be applied when the media query list evaluates to false, although that might be covered by
> section 4.1. (I’m not sure if @import with a media query counts as a "conditional rule" as it’s not defined in css3-conditional.)


> A terminology nitpick in section 3. Example 3 says
>> The multiple style rules of this example:[…]
> It should say "The multiple declarations" or "The style rule". css3-syntax defines "style rule" as the thing that has a
> selector and a {} delimited block of declarations. CSS 2.1 called it a ruleset.


> In section 4.1:
>> A declaration applies to an element if: […]
>> The remaining declarations form, for each property on each element,
>> an unordered list of values.
> It might be my English being weak, but I first read "The remaining declarations" as "those that do not apply" (those remaining
> after we took away those that apply.) while the intended meaning is clearly the opposite.
> I suggest changing the latter sentence to "The declarations that apply form, […]"


> Also, I find confusing that these lists are "unordered" while their "order of appearance" is used later in the cascade. In
> some versions of WeasyPrint, the implementation works by building ordered lists (in order of appearance) and then using a
> stable sort with a key based on origin, importance and specificity.


> Section 4.3.2 defines inheritance on elements and pseudo elements. Should it also mention or define inheritance on page boxes
> and page-margin boxes, or should that remain in css3-page? Are there other CSS modules that affect inheritance?

It should remain in css3-page.

> Section 5 suggests that specified, computed, used and actual values all apply to elements, while the latter two only apply to
> boxes. I’m not sure how to rephrase this.

Me, neither, but I tried. :)

Here's the diffs, let me know if it's better:


Received on Monday, 17 December 2012 10:12:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:24 UTC