This is a page from the Cascading Style Sheets Working Group Blog. Some other places to find information are the “current work” page, the www-style mailing list, the Future of CSS syndicator, and the issue list on Github.
Do you want to know how the CSS WG works? Fantasai has written about:csswg, An Inside View of the CSS Working Group at W3C.
Spent some time explaining to the IBM accessibility guy that
David Baron will be clarifying the spec to make this clear.
Discussed two-token lookahead problem caused by the new fallback color syntax. No resolutions.
fantasai had an action item from the last F2F to draw up a parse-time constants counter-proposal to CSS Variables. This was completed and presented.
Håkon presented a proposal for a border-parts property, which defines an on/off mask over the border as a series of lengths. There was lots of discussion about syntax, and lots of skepticism about its usability and utility.
Note that the ‘direction’ property is often set by rules in the UA style sheet based on mark-up in the document, as recommended in CSS 2.1 [CSS21] section 9.10 (“Text direction: the ‘direction’ and ‘unicode-bidi’ properties”).
When formatting content in the page model, some content may end up outside the current page box. For example, an element whose ‘white-space’ property has the value ‘pre’ may generate a box that is wider than the page box. As another example, when boxes are positioned absolutely or relatively, they may end up in “inconvenient” locations. For example, images may be placed on the edge of the page box or 100,000 meters below the page box.
We’ve published a new official Working Draft of the CSS Backgrounds and Borders Module Level 3. Some major changes from the last draft include:
border-radiusbackground-position syntax for positioning offsets from corners other than the top leftbackground-clipcover and contain values for background-size that proportionally stretch the background image to either cover or be contained by the entire background areabackground shorthandCheck it out and send us some feedback. This draft is in the stabilizing phase: the next publication should be the last one before Candidate Rec, and we’d rather get your comments this round. The plan is to do some more polish work, respond to comments and suggestions, and then publish a Last Call with this feature set near the end of the year.
Reviewed status of LC specs:
Discussed grammar of @page wrt @margin-box rules. Created CSS 2.1 Issue 71 in response.
Resolved: @rules inside declaration blocks are ignored if between declarations (i.e. at the beginning of a declaration before the property), invalid if within declarations. (CSS2.1 Issue 71)
Filed ISSUE-61 against CSS3 Fonts spec
John Daggett presented an overview of CSS3 Fonts including a discussion of:
border-length feature, alternative syntaxes, and moving it to Backgrounds and Borderstext-replacement proposal. Several members strongly feel it does not belong in CSS but rather as part of a transformation language that uses CSS syntax.bookmark feature. Several members are skeptical that this belongs in CSS as it’s conveying semantic, not stylistic, information.float.block-progression to block-flowbackground-positionbackground-position in editor’s draft: 4 values that require two keywords, allow zero values to be skipped.transparent keyword to border-image rejected. (ISSUE-28)background-clip and background-origin<br> and how it behaves in the CSS formatting model.Resolved: For CSS2.1 Issue 14 replace
The bottom margin of an in-flow block-level element with a ‘height’ of ‘auto’ and ‘min-height’ less than the element’s used height and ‘max-height’ greater than the element’s used height is adjoining to its last in-flow block-level child’s bottom margin if the element has no bottom padding or border.
with
The bottom margin of an in-flow block-level element is adjoining to its last in-flow block-level child’s bottom margin when:
- the element’s specified ‘height’ is ‘auto’,
- the element’s used height is the same as it would have been if the specified values of ‘min-height’ and ‘max-height’ were their initial values
- the element has no bottom padding or border
Resolved:
Proposal accepted for CSS2.1 Issue 32 (@ not followed by a valid identifier).
Resolved: No change for CSS2.1 Issue 35
Resolved: Proposal accepted for CSS2.1 Issue 42 (Static position should also assume clear: none)
Resolved: For CSS2.1 Issue 46 (Clarify how media queries qualify style rules) accept proposal plus prepend “The import only take effect if the target medium matches the media list.” to last paragraph in 6.3
Resolved: Proposal accepted for CSS2.1 Issue 48 (Remove outdated parts of bolder/lighter definition)
Resolved: For CSS2.1 Issue 49 (Clarify computed value for bolder/lighter) leave behavior of mixed nested bolder and lighter undefined and add the following note:
Note: A set of nested elements that mix ‘bolder’ and ‘lighter’ will give unpredictable results depending on the UA, OS, and font availability. This behavior will be more precisely defined in CSS3.
Resolved: For CSS2.1 Issue 52 say that page-break-* “may apply to other elements” besides block-level elements.
Resolved: Proposal accepted for CSS2.1 Issue 51 and CSS2.1 Issue 62.
Resolved: For CSS2.1 Issue 70 change “Vertical margins of elements with ‘overflow’ other than ‘visible'” to “Vertical margins of block formatting contexts (such as floats and elements with ‘overflow’ other than ‘visible’)”
Discussed progress on CSS2.1 Test Suite
Resolved: Periodically publish Editor’s Draft of CSS2.1 that incorporates errata.
Full minutes:
Resolved: Make proposed editorial changes to Mobile Profile and republish.
Resolved: Text decoration should propagate through table elements. (CSS2.1 Issue 56)
Resolved: Accepted proposal for CSS2.1 Issue 54 (specify left or right position for list markers based on ‘direction’) with the word “elements” replaced by “list items”.
Browse by date:
Browse by category: