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, and the Future of CSS syndicator.
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.
will-change
.subgrid
to level 2 of Grid would create accessibility issues that would be hard to rectify even after level 2 is released. TabAtkins stated that he still believes that the inclusion of subgrid
in level 1 will cause too much of a delay to implement before shipping. The discussion will continue on the mailing list with sylvaing recommending a focus on use-cases instead of general speculation on what adopters may or may not do.keyframes
all revolved around reaching consensus on how browsers implement the spec. Sylvaing will solicit feedback from the browsers to ascertain the best path to compatibility and then move to solve the other issues.custom-ident
values, but there still isn’t a clear path on how to decide what other keywords should be excluded. Discussion will continue on the mailing list.The CSS Working Group has published a Last Call of CSS Flexible Box Layout Level 1 in order to gather feedback on recent changes. Flexbox is a new layout model for CSS: the contents of a flex container can be laid out in any direction, can be reordered, can be aligned and justified within their container, and can “flex” their sizes and positions to respond to the available space. This is an update to fix various problems, particularly in the layout algorithm, found through implementation review and experience during the Candidate Recommendation phase. The CSSWG is not revoking the call for implementations: we’re just issuing an LCWD to process the changes.
To help with review and with correctly updating implementations, exact diffs since the original Candidate Recommendation, and their justifications, are available in the Changes section. A Disposition of Comments is also available. The Last Call comment period ends 22 April 2014: please either send comments by then, or request an extension.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-flexbox]
) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
block-size
and inline-size
in Writing Modes.@scope
.The CSS Working Group has published Candidate Recommendation of CSS Writing Modes Level 3 and invites implementations. CSS Writing Modes Level 3 defines CSS handling of various international writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left (e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and vertical (e.g. Asian scripts).
Changes since the last Working Draft include renaming text-combine-horizontal
to text-combine-upright
and a handful of clarifications.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-writing-modes-3]
) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.) We would especially appreciate reviews of the layout rules, since they’re complex and likely to still have errors…
The CSS Working Group has published a Candidate Recommendation of CSS Shapes Module Level 1. The specification describes geometric shapes for use in CSS, and allows these shapes to be applied to floats. When a shape is applied to a float, inline content wraps around that shape instead of the float’s margin box.
The only changes from the last Last Call draft were in code examples.
All changes to the draft over the last few publications are listed in the Changes section.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-shapes]
) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
--
prefix to define var in Syntax.namespacerule
being unnecessarily limiting for authors. Some work arounds were discussed and feeling seemed to be a bit mixed. Conversation will continue on the mailing list.subgrid
from level 1 of Grid. TabAtkins stated he agreed in principal with her arguments, but didn’t think shipping could be delayed long enough to get subgrid
ready. Due to lack of time the conversation will continue on the mailing list.inline-something
and block-something
with “something” TBD ASAP.
custom-ident
. A desire was raised to have a global list of restricted values as well as a desire to ensure that the solution minimize opportunity for confusion for authors or spec writers.custom-ident
is restricted only in cases where actually ambiguous parsing-wise. Specs referencing it should be clear about what is excluded.fill-box
and stroke-box
.
The CSS WG has published a Candidate Recommendation of the CSS Syntax Module Level 3. This module describes, in general terms, the basic structure and syntax of CSS stylesheets. It defines, in detail, the syntax and parsing of CSS – how to turn a stream of bytes into a meaningful stylesheet.
This is a complete rewrite of the obsolete 2003 draft. It describes CSS tokenization and parsing in imperative recursive descent style, and exhaustively covers error handling. Additionally, the An+B syntax used in :nth-child() and related Selectors is now described in terms of the same tokenizer as the rest of CSS.
Changes since the Last Call Working Draft are listed in the Changes section.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-syntax]<<
) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
shadow-deep
. TabAtkins and Fantasai will meet in person later this week and report their conversation back to the mailing list.Browse by date:
Browse by category: