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 CSSWG has published an updated Working Draft of CSS Box Alignment Level 3. This module defines extends the Flexbox alignment properties to apply to all layout models and adds additional controls for logical positioning, space distribution, and handling overflowing elements.
This is the vertical centering module, people.
This module’s syntax and functionality is in the process of stabilizing now and we need your feedback. Think of all the cool things you could do with the new alignment properties! Imagine them! Examine them! Make examples! Write rants! And tell us what is awesome and what is stupid so that we can fix it to be better before it gets locked down in shipped browsers.
Changes since the last Working Draft are listed in the Changes section.
As always, ideally send feedback to the (archived) public mailing list email@example.com with the spec code (
[css-align]) and your comment topic in the subject line. Alternatively, post your comment here or in the more discussion-friendly CSS3.info cross-post. (Or, if that’s still too scary, email the editors directly.) Please do not expect us to go fishing for your comments in the ether. We won’t know it’s there and we will therefore deliberately and mercilessly ignore it. If it’s on your blog, email the link or post it as a comment. It’s super not that hard. Thanks.
text-overflowshould be start/end instead of right/left
::selectionand Pseudo-Elements issues
text-shadowwill be added as properties
appendRulealways add at the end of the keyframe no matter if the key already exists.
CSSGroupingRule” bug (available here).
overflow-blockare fine as they are. No change for current concerns.
item-positionand move it back later once the group comes to a decision.
deleteRulewill apply to the last keyframe with a specified value (no change to Animations spec)
imagein addition to
uriand refer to image production as part of the text. (Issue 44)
:not()is the specificity of the most specific
:focus-withinthat matches on the same things as
:focus, plus parents, including if there are Shadow DOMs
:activeshould propagate from the labeled control to the label, in addition to the other direction.
text-overflow, the conversation about handling items where, due to other properties, the text can’t overflow ended up being too complex for the time on the telecon and will go back to the mailing list.
flex-basis: autochanges (auto means
main-sizeand add a keyword for automatic sizing)
urange(available here) could move to the Fonts spec. There was disagreement between jdaggett and TabAtkins as to if this additional normative text was necessary for the spec, however, implementers stated that they did want the text available to them. A compromise was reached where it would be in an appendix so that regular authors wouldn’t normally encounter it.
urangedefinition to an appendix in the Fonts spec.
content: iconand the icon property from CSS-UI
nav-indexfrom level 3 of CSS-UI and put it on a wiki
nav-indexto the wiki here.
text-overflowissue, so discussion will continue on the mailing list.
::spelling-error, including information pertaining to the security concerns.
contentproperty should stay where it is.
:hoverpseudo was wrong and will be changed.
::selectionshould inherit from.
@keyframerules except the animation timing function (where we have explainer text already)
@keyframesnames and will throw an error when set through the OM
findRule/deleteRulereturn/delete the last rule with the specified key.
Browse by date:
Browse by category: