Bert Bos,
CSS contactLast updated $Date: 2008/10/02 13:21:40 $ GMT
(This page uses CSS style sheets)
W3C and the CSS Working Group publish information about the specifications under development in various ways. This page is the working group's weblog (blog). Other places to find information are the “current work” page, the www-style mailing list.
background-color property to solve ISSUE-65.
Rationale: While this makes the property slightly harder to read and requires typing out transparent in full every time, it solves the 2-token lookahead problem very simply.background-image should determine the number of background layers. ISSUE-74. Rationale: Less likely to cause confusion for authors or introduce unintended behavior through the cascade. Pending: Since Apple has already implemented the other option, we are waiting to hear back from them. If they agree this issue will be resolved as above.:hover to apply to an element because its child is designated by a pointing device, then it's possible for :hover to apply to an element that is not underneath the pointing device. Rationale: The spec leaves undefined whether the :hover state is passed up the DOM tree. Browsers all treat it that way and websites would break if that were changed. We're adding this note to clarify to readers that it :hover can match an element even if it not hovered over if its child is positioned outside its geometric bounds.:active, but made no resolutions about it.an+b grammar in ISSUE-66 to the Selectors spec.The portion of a child element that occurs on the first line inherits properties applicable to the ::first-line pseudo element; for properties not applicable to the ::first-line pseudo element, the inheritence is from the non-pseudo-element parent of the ::first-line pseudo element. The portion of a child element that does not occur on the first line always inherits from the parent of that child.
page should be a non-inherited property. auto means look to the nearest non-auto ancestor and use that page value. Implementations that do inherit 'page' will be considered conformant to CSS3 Paged Media (since that is the currently-specified behavior), but not CSS4 Paged Media. We will add warning authors that the behavior of 'page: auto' would be unpredictable when used within an element with 'page: somethingelse'.Discussed overflow of multicolumn elements: whether new columns should be madd off to the side, or whether a new row of columns should be created as overflow below.
To create a layouts where a new set of columns are created below the first, we really would need a column-length property or somesuch and allow the height to be auto, otherwise the new columns will overflow the multicol element and overwrite later content.
Either way, multicolumn layout is not very usable on the screen because it's designed for paginated media. So we discussed the idea of overflow-style: paginate to create paginated layouts on the screen. (It would fall back to scrolling behavior on down-level clients.)
fantasai noted that the column width algorithm should define available width such that the UA can consider the available width on the page if that is less than the available width of the element.