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.
The CSS Working Group has published several updated Working Drafts:
This module describes how the CSS formatting box tree is generated from the document element tree and defines the display property that controls it. Additions since CSS2 include: a
flow-root value to create a block formatting context root (BFC), a
contents value to discard the element’s box but keep its children, inline list items, a
run-in layout model slightly less wonky than the one proposed in CSS2.0. Significant changes since the last publication are listed in the changes section.
We anticipate this being the last draft before the transition to Candidate Recommendation, therefore this is the “last call” for comments.
stretchto match the similar
stretchoption in the alignment properties. Remaining work prior to Candidate Recommendation includes addressing issues in the extrinsic sizing section (which includes
stretch) and handling replaced elements’ interaction with the intrinsic sizing keywords.
last-baseline. See discussion for rationale.
place-*as shorthands for
unsafein Issue 1001 to allow better integration with the shorthands.
We are hoping to take this module to CR this year. In the meantime, we are looking for
As always, please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list email@example.com with the spec code (
[css-align]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
text-decoration-skip-inkwith at least values of auto and none and have it cascade separate from shorthand. We will have some normative text describe how auto works, but we’ll figure the details out in the future. Do this in L4.
speak: automatches the AAM computation in how it takes
display: noneinto consideration
line-height-stepproperty would lead to an author accidentally getting the double height in a browser he/she didn’t test against due to a variation on the value of
line-height:normalcaused by each browser calculating it slightly differently.
line-height:normalis a TBD fixed value when the user sets
line-height-stepto anything other than initial. If this proposal does go forward the initial value of
line-height-stepshould be none.
line-height:normalsuddenly stops working.
background-repeat-x/ydue to web usage several browser vendors didn’t want to add the property because they didn’t feel there was such a strong need. It is Chrome’s responsibility to gather more data to either persuade other vendors to implement it or to decide that they can remove it.
auto|always|none) and inform the a11y TF.
-ms-scroll-chaining, but it wasn’t ready for a resolution. The latching behavior done by webkit and Chrome should be added to the proposal or at least able to be done with the properties. It was agreed that the name will need to be improved. This will be added to the F2F agenda.
-webkit-device-pixel-ratioshould be defined in the Media Queries spec. Several people had no wish to define it since it’s an alias to the resolution media query, but there was concern that that’s compatibility hostile since currently you need
-webkit-device-pixel-ratioto be web compatible.
Browse by date:
Browse by category: