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.
justify-content: auto-> start / stretch (on grid / flex items)
justify-content: stretch-> flex-start (on flex items)
align/justify-items: auto-> start/stretch (depending on ‘display’)
border-image. Several implementors said they would be willing to change back to the spec behavior once the two Google properties are fixed as long as there isn’t a long tail of other sites relying on the bug. TabAtkins will report back to the group in January with any updates on a timeline for the fixes.
align/justify-contentwith bikeshed pending
polar-angleand animations in relation to the Round Display spec. The best path forward depended on if the computed value of
polar-angleis an angle or stays as a keyword. Jihye will look for use cases of the property to determine which solution is the right one and present her use cases and conclusion on the mailing list.
The CSS Working Group has published an updated Working Draft of the CSS Device Adaptation Module Level 1. This specification provides a way for an author to specify, in CSS, the size, zoom factor, and orientation of the viewport that is used as the base for the initial containing block.
This update contains changes accumulated since 2011, so there’s quite a few of them.
Changes since the last Working Draft are listed in the Changes section.
As always, please send feedback to the (archived) public mailing list
with the spec code (
and your comment topic in the subject line.
(Alternatively, you can email one of the editors and ask them to forward your comment.)
system-uiin Fonts 4
pre-wrap-auto, but the right people to come to a conclusion weren’t available, so the conversation will continue on the mailing list.
word-break: break-allneeded re-working, though there wasn’t a clear decision on the right direction. Koji and fantasai will come up with a proposed change to the spec referencing UAX14 and see what the group thinks of it.
pre-wrap, disallow wrapping before the first space.
vertical-rlmode, but webkit plans to change to be more consistent with the proposal.
endfor positioning needs a consistent decision between all 2d positioning, not just for floats. It was added to the TPAC agenda.
autovalue for alignment. The spec will be left as-is for now and fantasai will look for more feedback, especially from authors.
forceto the page, column, and region keywords, still needs to be discussed either on a call or at TPAC.
polar-anchor(available here). Generally there was agreement that this was useful and the right direction for this property. There was concern that the property could still cause overflow even though this was designed to prevent it.
autoseemed like it could be what prevents the overflow, but was under-specified in this proposal and needed to be fleshed out more.
polar-anchorwith issues for better specifying
scale(available here) to the Transforms spec.
:focus-ringto allow authors to only style the focus ring when the browser would normally trigger a focus ring as a way to narrow-down the more generic
:focuspseudo-class. There were concerns that this would have negative accessibility implications, but it was argued those implications exist within :focus and should be addressed there- this makes the problem no worse than what already exists. The name seemed problematic to some people so it may need bikeshedding later.
:focus-ringto Selectors 4 or 5.
svgin level 4 of CSS UI.
resizeas described for level 4.
sideways-rightused to do. State that for legacy compat UA may support
sideways-rightvalue that does the same thing and computes to
Browse by date:
Browse by category: