Updated CR of the CSS Containment Module Level 1
The CSS WG has published a Candidate Recommendation and invites implementations of the CSS Containment Module Level 1. This CSS module describes the contain property, which indicates that the element’s subtree is independent of the rest of the page. This enables heavy optimizations by user agents when used well.
This update to the previous CR brings bug fixes and clarifications. No new feature has been added, nor has any feature been removed. All changes since the previous CR come with a test in Web Platform tests.
Significant changes sine the last CR are listed in the Changes section. A disposition of comments is available.
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-contain]) 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-05-23
- Resolved: Add fr unit support as min arg inside minmax for Grid L2. (Issue #2611)
- Having a three value syntax for minmax (Example:
minmax(5em, 2fr, 250px)) will be considered later and separately from the rest of Issue #2611.
- Resolved: Accept the edits around subgrid and grid-gap (Issue #2285)
- Resolved: Accept the proposed changes (to skip unicode punctuation characters for emphasis marks with a few exceptions) and follow up with unicode [on why there are exceptions] (Issue #839)
- Resolved: Updated publication of css-text-decor-3 CR
- Resolved: Accept proposal (A block container that establishes a new block formatting context is considered to have a used display value of flow-root.)
- Resolved: Defer to css-pseudo-4 to address [interaction between display:contents and ::first-line] as part of more rigorously defining ::first-line cascading/inheritance. (Issue #1310)
- Resolved: Defer Issue #1810 and Issue #2365 to later.
- There are only a few issues remaining for CSS Display so the editors plan to request CR possibly as early as next week. Anyone planning to do a spec review before that transition should do so soon.
- Resolved: Accept the proposal in Issue #2682 (make the existing word-wrap/overflow-wrap property affect intrinsic sizing)
- Resolved: Accept the edits to clarify various meanings of ‘formatting context’ (Issue #1457)
Full Meeting Minutes
Minutes Berlin F2F 2018-04-10 Part III: Sizing, Flexbox, Overflow
Sizing
- Resolved: Treat indefinite percentages in min-width and min-height as 0. (Issue #2384)
- Resolved: Add a note to the spec explaining this problem (adding a ‘size’ shorthand for ‘width’/’height’) and move this issue to level 4. (Issue #820)
- Resolved: Publish a new WD of Sizing with all current resolutions edited in.
Full Meeting Minutes || Specs Referenced: Sizing L3, Sizing L4
Flexbox
- Resolved: Tables defines used min-size to fold in its min-content size where necessary (for
table-layout: auto); Flexbox ensures it is hooked up to this terminology when looking up an item’s minimum size.
- Resolved: Have an initial ED of Flexbox L2, defining combination w/ additional alignment values and gap properties.
Full Meeting Minutes || Spec Referenced
Overflow
- Resolved: Allow 2 values on the overflow property in physical x/y order for any existing values.
- Resolved: Add block and inline longhands to overscroll-behavior.
- Resolved: text-overflow and resize apply to elements with
overflow: clip just as they apply to elements with overflow: hidden.
- Resolved: When
overflow: clip is propagated to the viewport it changes to overflow: hidden the same way ‘visible’ is changed to ‘auto’
Full Meeting Minutes || Spec Referenced
Minutes Berlin F2F 2018-04-10 Part II: Spacial Navigation, CSS Floats, Grid L2, Grid L1, Box Alignment
Spacial Navigation
- Jihye showed a demonstration of how the spec has progressed so far (available here)
- Much of the current spec isn’t about CSS, but it has raised questions about terminology and making it easier to refer to scrolling concepts.
- It was suggested that all the definition of terms occur in CSS Overflow to make it easier to reference terms.
- There’s significant interest in having this spec assist accessibility concerns.
- The group did not think that adding information about hit testing would be valuable.
- Exposing a new Media Query that would give data on interaction media feature navigation raised concerns about possible fingerprinting. If there are strong use cases the group will reconsider.
- Resolved: Add the definition of the border shape edge to Borders and Backgrounds L3 (Issue #2324: Missing box terminology).
Full Meeting Minutes || Specs Referenced: Spacial Navigation, Backgrounds & Borders, CSS Overflow
CSS Floats
- Originally there were three proposals to address issue #2452 (What happens when a bfc height grows such that it intersects with a lower-placed float that was not considered when choosing its width):
- Attempt all possibilities until one fits (what Firefox does)
- If it doesn’t fit you try one more layout
- Put the BFC under the floats (what Edge does)
- Option 3 is the most performant, but option 1 was what users would expect. Option 2 was a compromise, but since no one implements it currently there were objections to resolving on it.
- The group agreed on Option 1 and will request more performance data from whomever implements so that they can re-open this if there is a significant performance issue.
- Resolved: The working group preference is to specify BFC float avoidance behavior to match the guidelines of what is spec in 2.1 for inline layout float avoidance behavior.
- Resolved: Start a CSS 3 Floats Module with dbaron and fremy as co-editors.
Full Meeting Minutes || Spec Referenced
Grid L2
- Author expectations and use cases were toward having the per-axis subgrid (Issue #2280) however several people needed more time to review the spec text so the group will revisit this issue later in the F2F.
- Resolved: Add an ar unit to the grid 2 spec for
align-content and justify-content. (Issue #1116)
Full Meeting Minutes || Spec Referenced
Grid L1
- The group believed that the Grid algorithm could still be adjusted to accomplish the use case in issue #2356; however the correct adjustments weren’t immediately clear. TabAtkins and fantasai will look into a post-processing step that was suggested and Florian will reach out to Bert to see if he has any insights.
- Resolved: Edit in Rossen proposal in issue #2177 “Spanners that cross tracks that have content-based mins AND flexible maxes only contribute content sizes to those tracks; otherwise they participate normally.”
- Resolved: Alignment and gaps in multicol behave exactly like grid and we will add a note explaining the concerns in the issue and how to solve them. (Issue #1420)
- Resolved: Remove these terms (
row-axis and column-axis) from the grid spec (Issue #1299)
Full Meeting Minutes || Spec Referenced
Box Alignment
- Resolved: Zero out percentages on non-sizing use of calc. (Issue #2297)
- Resolved: Fallback alignment for last-baseline is ‘safe end’ (Issue #1611)
- Resolved: Publish a new WD of Alignment with the one edit from the baseline resolution.
Full Meeting Minutes || Spec Referenced
Minutes Berlin F2F 2018-04-10 Part I: 2018 Snapshot, F2F Planning, Accumulating Compat Issues via Ambiguity, Page Floats, CSS Sizing, CSS 2.1, Overscroll, Writing Modes
2018 Snapshot
- Resolved: Merge text describing cleared-to-ship features after editorial fixup.
- Resolved: Proceed with publishing snapshot as-is including the open issues.
Full Meeting Minutes || Spec Referenced
2019 F2F Planning
- Resolved: We will have a late Jan or in Feb 2019 meeting, possibly in Sydney.
- The group generally favored a meeting every 3 months which will mean that depending on TPAC there could be 3 or 4 meetings in a year.
Full Meeting Minutes
Accumulating Compat Issues via Ambiguity
- Everyone agreed that they’d like this to not happen again.
- Many felt that the percentage margins issue was not typical, because this case was intentionally made ambiguous due to a split in both author and implementor opinion, resulting in a complete lack of consensus on the right way forward.
- Looking back, this may have been avoided if someone had taken the time to specify a property to replace the percentage margin hack.
Full Meeting Minutes
Page Floats
- Resolved: Add rachelandrew and florian as editors to page floats.
Full Meeting Minutes || Spec Referenced
CSS Sizing & CSS2.1
- Resolved: Add an issue and a fix for CSS2 to disambiguate inner vs outer width. (Issue #2458: Definition of box-sizing in css-sizing)
- tantek was actioned to make the needed edits to CSS2
Full Meeting Minutes || Specs Referenced: CSS Sizing, CSS2.1
CSS Overscroll
- There is already a resolution to move this spec into the csswg-drafts, but we’ll keep waiting on the current WICG editors to join the CSSWG.
Full Meeting Minutes || Spec Referenced
Writing Modes
Minutes Telecon 2018-05-09
- Resolved: If you have a fragID in @font-face src, and you don’t understand the fragID syntax, you don’t download the font. (Issue #2566)
- Resolved: If fragID is valid, but not found in the resource, skip as if couldn’t load resource. (Issue #2566)
- Resolved: Add
format signifier for font collections, similar to variations. (Issue #2566)
- Resolved:
css-font-loading, level TBD (Issue #520)
- Resolved: Add
clamp(min,mid,max) with min winning over max (Issue #2519)
- Resolved: dppx is canonical unit [in serialization of
resolution] (Issue #2241)
- Resolved: Add often-rendered-as sentence to pointer definition. (Issue #1936)
Full Meeting Minutes
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.)
![[Photo: group photo of the CSS working group in Lyon, France]](/Style/CSS/csswg-2010.jpg)
Contact: