W3C home > Mailing lists > Public > www-style@w3.org > July 2007

[CSS21] Some Possible Issues

From: fantasai <fantasai.lists@inkedblade.net>
Date: Tue, 03 Jul 2007 11:05:43 -0400
Message-ID: <468A65C7.5060909@inkedblade.net>
To: www-style@w3.org

Some issues that came up while compiling the changes list:


   I can't find text that says whether the used value or the computed
   value of border-width becomes zero when border-style is none. CSS2
   was explicit about this being the "computed width" and afaict Opera
   and Mozilla do interpret it that way even though the meaning of
   "computed value" has changed.


   14.2 first paragraph says a background is "either a color or an image",
   but we allow both. It should be "a color and/or an image".

   This paragraph:
    # The tiling and positioning of the background-image on inline elements
    # is undefined in this specification. A future level of CSS may define
    # the tiling and positioning of the background-image on inline elements.
   appears twice, once under 'background-repeat' and once under
   'background-position'. Perhaps once is enough?
   Also, shouldn't this be restricted to "inline elements with more than one
   generated box"?

   (Bert, there's a question in the spec (in a comment) about whether values
   like "50% left" are still disallowed with the new text. Yes, they are
   disallowed because we fixed the syntax definition in the Value field to
   disallow them.)


   3.2 item 4 says
    # For each element in a document tree, it must assign a value for every
    # applicable property according to the property's definition and the
    # rules of cascading and inheritance.
   Strike "applicable": it should be every property.


   In reverting to CSS1's prose we've made it very unclear what exactly
   inherits for font-weight.
   The spec currently says
     "Child elements inherit the resultant weight, not the keyword value."
   Given that we carefully adjusted the definition of computed value for
   this property, this sentence should be removed.

generated content

   12.3.2 has text saying:
    # A 'close-quote' that would make the depth negative is in error and is
    # ignored (at rendering time): the depth stays at 0 and no quote mark is
    # rendered (although the rest of the 'content' property's value is still
    # inserted).
   This should apply to 'no-close-quote', too.

paged media

   In 13.2.2, in CSS2 and CSS3 Paged Media we required :left and :right to
   be honored even for single-sided printing. That paragraph has been
   removed, so now a) it is undefined what happens on single-sided printers
   when :left and :right declarations are present and b) it's no longer
   possible to get the double-sided printing effect by re-feeding all odd
   pages to the printer to get their other side printed.

   In 13.2.2 The spec says
     # Margin declarations on left, right, and first pages may result in
     # different page area widths. To simplify implementations, user agents
     # may use a single page area width on left, right, and first pages.
     # In this case, the page area width of the first page should be used.

   What exactly does it mean, "use the page area width of the first page"?


   We have a statement
     # Internal table elements do not have margins.
   But "internal table elements" is not defined. Is a table box (which is
   internal to the outer table box) an "internal table element"?


Bert, there's a comment
<p>[What about the "lost errata" for clip? See
<a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2001OctDec/0218.html">David</a>
<a href="http://lists.w3.org/Archives/Member/w3c-css-wg/2001OctDec/0235.html">Eric</a>.
Were these addressed? (From a cursory glance it seems so to me.)
Can we remove the comment?

Received on Tuesday, 3 July 2007 15:05:53 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:29 UTC