CSS Grid Level 2 Updates: Per-axis Grid and ‘ar’ units for gutters
The CSS Working Group has published an updated Working Draft of CSS Grid Level 2. Level 2 expands Grid by adding “subgrid” capabilities for nested grids to participate in the sizing of their parent grids; and aspect-ratio–controlled gutters.
The main goal of this level is to have a completed spec for subgrids as soon as possible—so while we might cull some other minor features from the list of requests, more complex feature requests will be deferred to Level 3. Changes from the last draft consist mainly of dropping the simplified “dual-axis” subgrid proposal in favor of the more powerful “per-axis” proposal and switching the syntax for aspect-ratio–controlled gutter justification to use ar units in place of bare numbers. We’ll be working through individual issues filed against these features going forward, such as control over gaps and interaction of parent/subgrid named lines, etc.
Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-grid-2]) 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 2018-04-25
- Resolved: Publish updated CR of css-contain-1
- The group began by discussing issue #2542 (Should we add scientific notation to CSS 2.1?) where an unintended consequence of a previous decision was to add a new feature to CSS 2.1. There was general agreement that there was no intent to introduce a new feature, but the larger question came to how to handle the Syntax section in CSS 2.1 (Issue #2224). Originally there were several proposals including removing the section, just adding notes, only changing the error handling portion, or turning the section informative and adding notes. Many of the suggestions raised process concerns as the group did not want to bring CSS 2.1 back to a WD, however after re-reading the process document it was clarified that feature removal would only require returning to CR.
- Resolved: Take 4.1, 4.2 and 4.4 in CSS 2.1, change them to informative notes, and add notes to those sections + appendix G showing where the newer work is being done. Links to newer works are informative notes. (Issue #2224)
- Resolved: We add a note to CSS 2.1 noting the presence of at least one new feature in the informative reference. We intend not to add any new features to CSS2. (Issue #2542)
- Resolved: Take current draft and revert to 2011 anchors. (Issue #2551)
- Resolved: Take dated 2011 rec and revert link changes. (Issue #2551)
- Resolved: http://www.w3.org/TR/TR/2016/REC-CSS2-20160412/ is what is currently at http://www.w3.org/TR/2011/REC-CSS2-20110607 and /TR/CSS2/ redirects to http://www.w3.org/TR/2011/REC-CSS2-20110607 and ChrisL may add a warning note about the 2016 links as he sees necessary (Issue #2551)
Full Minutes
CSS Box Alignment Level 3 Updated WD
The CSS Working Group has published an updated Working Draft of CSS Box Alignment Level 3.This module contains the features of CSS relating to the alignment of boxes within their containers in the various CSS box layout models: block layout, table layout, flex layout, and grid layout. It also includes the new cross-module gap properties (row-gap, column-gap, gap).
This update fixes various errors in the previous draft. At this point only one issue is open, and the biggest known problem is an insufficient number of illustrations, particularly in the baseline alignment sections. Other than that, we’re hoping we can wrap up and request a transition to CR soon. Changes since the last Working Draft are listed in the Changes section.
Special thanks to Melanie Richards for adding illustrations to the Positional Alignment section, especially as they were unexpectedly tricky to diagram due to internationalization-related complexities. Further editorial advice and/or diagrams that would help make this draft easier to understand are very welcome.
Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-align-3]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Display Level 3 Update
The CSS Working Group has published an updated Working Draft of CSS Display Level 3. CSS Display describes how the CSS formatting box tree is generated from the document element tree and defines properties that control the types of boxes thus generated.
Changes this time around are fairly minor, mostly just tightening up definitions; see the Changes section. There are a handful of open issues, mostly editorial, but otherwise we expect (hope?) the draft will transition to CR in roughly its current form pretty soon.
Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-display-3]) 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 2018-04-04
- Resolved: Publish a new WD of Fonts L4
- Resolved: Extend value definition syntax to handle value ranges and possibly other syntactic restrictions, syntax TBD. (Issue #355)
- Resolved: Accept change set for defining box ↔ element style correspondence (Issue #1643)
- Resolved: Add the appendix for Box Construction Guidelines for Spec Authors to Display 3 (Issue #1643)
- Resolved: Run-in flow-root blockifies to block and not flow-root. (Issue #1715)
- Resolved: Treat
display:contents as display:none for MathML. (Issue #2167)
- Resolved: We define how SVG elements interact with
display:contents based on SVG defined categories. We will add a new issue about what to do with attributes. (Issue #2118)
- Resolved: Keep this note (The display property has no effect on an element’s semantics: these are defined by the document language and are not affected by CSS. Aside from the none value, which also affects the aural/speech output [CSS-SPEECH-1] and interactivity of an element and its descendants, the display property only affects visual layout: its purpose is to allow designers freedom to change the layout behavior of an element without affecting the underlying document semantics.) in Display 3 (Issue #2335)
- Resolved: Pending AmeliaBR edits, publish a new WD of Display 3.
- Resolved: Specify the current behavior in all the browsers except Edge. Just don’t use
repeat in grid serialization. (Issue #2427)
- Resolved: Remove the UI defined bit and go with 1em for computing normal in multi-col. (Issue #2145)
Full Meeting Minutes
Minutes Telecon 2018-03-28
- Resolved: Serialization of the repeat() MUST use the repeat syntax. (Issue #2427)
- Resolved:
overflow:clip is a paint time only operation and we shouldn’t require that an element with overflow as clip in either direction be a BFC nor a scroll port. (Issue #1971)
- Resolved: If you attempt to get a
computedStyleMap or use a computedStyleMap on an element not in the document it throws. (Houdini Issue #659)
- Resolved: Style maps of elements moved between documents throw. (Houdini Issue #659)
- Resolved: Clear gradient color stops with two locations for shipping. (Issue #2439)
- An issue (Issue #2438) was created to make progress improving the test suite documentation. Everyone is encouraged to review and contribute on the thread.
Full Minutes
Minutes Telecon 2018-03-21
- Resolved: Spec Gecko’s behavior at the ends of lines in display text for issue #1997 (white-space collapse at end of line: test case and queries).
- Resolved: Add a use-font (name to be bikesheded) keyword for these text decoration metrics. (Issue #2376: Add use-font keyword for text-decoration-width & text-decoration-offset)
- Resolved: Simplify the definition of break-spaces as in this commit for Issue #2033 (overflow-wrap: break-spaces can effect behavior even when there are previous breaking opportunities in the line)
- Originally the proposal for Issue #1484 (letter-spacing computed values don’t reflect reality) was to have normal compute to normal but behave as 0 as this was how browsers were believed to currently behave. AmeliaBR created a codepen which showed
getComputedStyle returning normal for 0 with several browsers, so the spec text would need to accommodate this behavior since it’s already interop.
- Resolved: We have the spec say computed value of letter-spacing is absolute length. There’s a quirk to
getComputedStyle where 0 serializes to normal and that doesn’t extend to the computed style map. (Issue #1484)
- Resolved: No change on issue #785 (Hyphenation usages in CJK).
- Florian will file bugs on browsers to fix/support the break-all keyword for the word-break property which minimizes the issue reported in this bug.
Full Minutes
CSS Text Decoration Level 4: First Public Working Draft
The CSS Working Group has published an updated Working Draft of CSS Text Decoration Level 4. The Text Decoration module contains the features of CSS relating to text decoration, such as underlines, text shadows, and emphasis marks. Level 4 adds controls for the offset and thickness of underlines, spread radius for text-shadow, and control over skipping punctuation and/or spaces.
This is an early-stage working draft, and significant changes are expected going forward, particularly to the skipping controls.
Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-text-decor-4]) 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 2018-03-14
- When TabAtkins tried to implement the previous resolutions on Houdini Issue #610 (Does the is2D design allow for inconsistent interpretation of CSSTransformComponents?) he realized that it introduced a lot of implementation complexity that wasn’t expected when the group resolved. Several people still wanted to have a better solution, though understood that the earlier resolution wouldn’t work. The group decided to roll back the resolutions and keep working at the F2F on a better approach.
- Resolved: Reverse the previous resolutions of this issue (Houdini Issue #610) and keep the spec as it currently is.
- Resolved: We allow 0 for column-width for the purpose of parsing, 1px is the minimum clamping value used for anything after parsing.
- Resolved: Add
stroke-color and stroke-width to the list of highlight properties.
- Resolved: Clarify stroke properties effect ink overflow and not layout.
- Resolved: if bidi resolution would result in splitting an inline in infinite space, it creates 2 fragments even if they end up adjacent due to line breaking.
Full Minutes
Minutes Telecon 2018-03-07
- Resolved: Request a transition to PR for CSS Color 3.
- Resolved: Publish updated CR of Fonts L3
- TabAtkins will edit in his proposal for Houdini issue #716 (Trim CSSResourceValue and subclasses to opaque objects for this level, punt rest to level 2)
- The group approved the pull request in Issue #2281 for the 2018 Snapshot. Issue #2388 (List features cleared for shipping) will still need to be resolved before publishing the snapshot.
- Resolved: Accept the edit in Issue #1132 with a clarification (for what counts as containing a percentage) and a hyperlinked term (as to what is a sizing property).
- dbaron reviewed the Mozilla-input Backgrounds & Borders 3 tests with issues and filed an issue to get help fixing the error they all had. There are still other tests that need to be reviewed.
- Resolved: Change the default behavior for emphasis marks in the current level of Text Decoration spec.
- Issue #2114 (Border width rounding clarification) requires more testing to discern if there is a common behavior that can be standardized around.
- Liam will file a bug on webkit to support setting list style to a fixed string. Either he or franremy will add the same to Microsoft’s user voice.
- Resolved: Clear
conic-gradient for shipping
- Anyone interested in speaking at the TYPO conference should reach out to Rossen or reply to the private thread.
Full Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: