Minutes Telcon 2013-09-25
- Resolved: RESOLVED: Publish CSS Compositing and Blending Level 1 as Last Call.
- Everyone will review GPCM and Page Floats for next week’s telecon.
- Resolved: TabAtkins to put
overflow: clip to new Editor’s Draft.
- Resolved: Use
doubles instead of float for matrix items.
- Remaining issues for
DOMMatrix, DOMPoint and DOMPointLiteral were deferred until next week.
- The group discussed the need for and use of
device-cmyk(). No conclusion was reached by the end of time, so the discussion will be continued on the mailing list.
Full minutes
CSS Syntax Draft Updated
The CSS Working Group has published an updated Working Draft of CSS Syntax. This module describes, in general terms, the basic structure and syntax of CSS stylesheets.
This is a complete rewrite of the obsolete 2003 draft. It describes CSS tokenization and parsing in imperative recursive decent style, and exhaustively covers error handling. Additionally, the An+B syntax used in :nth-child() and related Selectors is not described in terms of the same tokenizer as the rest of CSS.
Changes since CSS 2.1 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.)
CSS Ruby Level 1 Published
The CSSWG published a Working Draft of CSS Ruby Level 1 this week. This module describes the rendering model and formatting controls related to displaying ruby annotations in CSS.
The new draft extends the model to handle HTML5 ruby markup, and adds details on box generation, layout, alignment and justification, white space handling, line breaking, and various other details. In addition, the CSS properties offering control over ruby layout have been reduced, simplified, and aligned better with existing CSS controls in other layout models. Significant changes since the 2003 version are listed in the Changes section.
Comments are welcome on all aspects of this draft. As it’s a rather radical rewrite of the old spec, this is essentially a “first” draft of the CSS Ruby model, and we would appreciate feedback on the correctness and reasonableness of all the newly-specified details.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-ruby]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Updates to CSS Grid Layout
The CSS Working Group has published an updated Working Draft of CSS Grid Layout Level 1. This CSS module defines a two-dimensional grid-based layout system optimized for user interface design.
There were lots of changes since the last Working Draft, including:
Renaming
As resolved in May as part of the Logical Directions Renaming, we’ve updated the grid placement longhand properties to be grid-row-start/grid-row-end/grid-column-start/grid-column-end with the shorthands grid-row/grid-column and grid-area. (We expect authors to use the shorthands most frequently.)
As discussed at the Tokyo F2F in June, we also renamed the grid-definition-rows/columns properties to grid-template-rows/columns, and changed grid-template to grid-template-areas. This gives all the properties defining the explicit grid the same prefix. (We also added a grid-template shorthand, for good measure.)
Shorthands
We adopted the grid shorthand syntax from the Template Layout module and added the ability to set values for auto-formatted grids. The template shorthand syntax allows authors to visually associate the various row and column measurements with their respective rows and columns in the named template areas.
Named Lines
The previous named lines syntax was pretty awkward, as pointed out in this thread. It also used strings as CSS-internal identifiers, which we don’t do anywhere else. We adopted the proposal from that thread, which was to switch to identifiers and use parentheses to group multiple names for the same position. This has the benefit of
- Using identifiers, consistent with the rest of CSS
- Providing visual grouping of names that identify the same location
- Allowing the named grid areas template syntax (which uses strings) to co-exist with named lines in the grid-template shorthand.
A more subtle change to named lines is that named grid areas now implicitly create named lines corresponding to their start and end edges, so you can more easily position something to the start or end edge of a particular named grid area without having to explicitly name those lines.
Other Changes
We’ve also clarified how absolutely-positioned items interact with the grid-placement properties, defined the static position of grid container children, rewrote and fixed errors in auto-placement algorithm.
And last but not least, we redesigned the subgrids feature, which allows alignment across the contents of a grid container’s immediate children.
Moving Forward
We still have some open issues, in particular some open discussion around the grid-auto-flow, that we hope to resolve soon. After that we expect most of the high-level design work to be complete, and then we’ll be digging into the gnarly layout details until we iron them all out. 🙂
Feedback
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-grid]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Telecon 2013-09-04
- Resolved: Change
UNICODE-RANGE token (in Syntax & CSS2.1) to be more restrictive in what it accepts, per Tab’s proposal. (No changes to Fonts.)
- Resolved: Transition CSS Fonts Level 3 to Candidate Recommendation.
- Resolved: Transition CSS Cascade Level 3 to Candidate Recommendation.
- Resolved:
text-combine-horizontal doesn’t disable font-variant: full-width. Revisit if fonts start to become popular that would benefit from this extra interaction.
- Discussed improving gradient stop color fixup rules for better transitions.
- Discussed handling Media Queries 3 errata.
Full minutes
Minutes Telecon 2013-08-28
- Resolved: Publish updated WD of Grid Layout.
- Resolved: Switch named lines syntax from
<string>+ to (<ident>+).
- Resolved: Accept
grid shorthand.
- Resolved: Drop
auto value of font-size-adjust.
- Resolved: Clarify in CSS3 Fonts that
font-size-adjust only affects used, not computed, value of font-size.
- Resolved: Fix errors in note wrt using ems vs. numbers for line-height, effect of
font-size-adjust on ex/ch.
- Discussed whether
ordinals should be on font-variant-numeric or font-variant-position. Summary of arguments:
font-variant-numeric: ordinals
-
- Doesn’t have fallback synthesis like superscripts/subscripts, so want to avoid associating with
font-variant-position.
- Related to typesetting numbers, so in
font-variant-numeric.
font-variant-position: ordinals
-
- Affects letters, not numerals/digits, so weird to put in
font-variant-numeric.
- Affects visual position/size just like superscript/subscript, so makes sense in
font-variant-position, despite lack of fallback synthesis.
- Resolved:
object-fit stays at-risk (for now), since no benefit to taking it off the list.
Full minutes
Minutes Telecon 2013-08-21
- Status updates:
- Counter Styles LC just received many comments, which will need to be processed before CR transition.
- Fonts CR transition discussions deferred to next week.
- Transitions and Animations waiting on edits.
- Resolved: Drag-and-drop pseudo-classes based on survey results as
:drop(active|valid|invalid) (write-in candidate with best argument).
- Discussed whether to allow syntax like
[rel=next,prev,up] in attribute selectors. No conclusions yet.
- Resolved: Accept work on scroll-snapping properties, initially as a separate module, potentially folded into another one later.
- Resolved: Shift CSS4 Color proposal to ED
- Discussed behavior of
outline properties. Two use cases conflict: focus outlines (original intended use case), and fake “borders”.
Full minutes
Minutes Telecon 2013-08-14
- Resolved: CSS escapes for surrogates produce u+fffd instead.
- Resolved: Switch Syntax to using the term “codepoint” instead of “character”.
- Resolved: Publish CSS Syntax L3 to replace /TR/css3-syntax
- Resolved: Add a
dense/sparse keyword to grid-auto-flow, defaulting to sparse.
- Discussed starting informal Grid Layout task force calls
- Discussed interaction of
text-align and text-align-last. Aligning on a shorthand-longhand relationship, details to be worked out on-list so that we can extend with first-line controls in the future.
- Resolved: Add Tab as editor to Font Load Events.
- Discussed how to define canonical serialization order of longhands for a shorthand in the property definition tables.
Full minutes
Minutes Telecon 2013-08-08
- Resolved: The precedence of font feature side-effects from other CSS properties is in-between
font-variant property and font-feature-settings property.
- Discussed interaction of
text-combine-horizontal and font-variant: full-width.
- Discussed various options for handling
text-combine-horizontal: all; applied to an element with child elements.
- Started CSSWG rechartering discussion, see also wiki.
- Requesting reviews/issues for Selectors 4
Full minutes
Minutes Telecon 2013-07-31
- Discussed proposal to allow justification in combination with explicit letter-spacing. Seem to have consensus around Part I of proposal, except for concerns from Bert.
- Plan to tie impact of
image-resolution‘s snap keyword to layout-affecting zoom; transforms and scaling-zoom would not have an effect. Tab to propose text describing the two different kinds of zoom in either Media Queries or CSS Device Adaption.
- Resolved: Allow image-resolution to accept two values (for X and Y axes) for resolution, to allow explicit values to match
from-image in capabilities.
- Resolved: Clarify spec that CSS units (not physical units) are used for resolutions taken from image data.
- Resolved: FPWD Matrix, with naming issues noted.
- Resolved: Box-fixup on internal table elements before flex item determination, unless further problems raised during LC.
Full minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: