CR of CSS Containment 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 is the first CR of this drafts. Implementations are encouraged, and feedback based on them much welcome. In particular, comments about interaction with other specifications would be very welcome, and you find desirable optimization opportunities that this technology fails to facilitate, the CSSWG would like to hear from you.
Significant changes are listed in the change section of the specification, and 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.)
First Public Working Draft of CSS Fonts Level 4
The CSS Working Group has published updated Working Drafts of CSS Fonts Level 4. This module defines new features regarding variable fonts, font loading timeline configuration, and color fonts support.
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-fonts]) 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 2017-07-26
- fantasai pulled a list of open Align issues to ensure they’re discussed.
- Bert reported that he’s done enough work on CSS 2 so that a discussion on how to manage it going forward can be added to the F2F agenda.
- Resolved: Option #1 from the Issue #1612 “Reduce the size of the alignment container by the size of the float’s margin box, then center the block in the remaining space (this is the behavior of HTML’s align attribute)”
- Resolved: Such alignments that overflow will not participate in last baseline alignment (Issue #1556)
- fantasai requested review on the text changes added to the spec to address Issue #1609: Intrinsic Size of Images with Intrinsic Aspect Ratio and No Size
- She also mentioned that Issue #951 (Define sizing of SVG Boxes with intrinsic aspect-ratio but no intrinsic size, in an auto-sized shrink-wrap parent) is on the F2F agenda for discussion so people can think about it in advance. AmeliaBR noted that many of these cases have been addressed in SVG so referring to that spec should be useful in this conversation.
- Resolved: Accept the edits proposed in Issue #1295
Full Minutes
Updated Working Draft of Motion Path Level 1
The CSS Working Group has published updated Working Drafts of Motion Path Level 1.
Motion Path Level 1 describes how graphical object is positioned and animated along an author specified path.
Most of the changes are influenced by merging some features from CSS Round Display. A list of significant changes can be found in Changes section.
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 ([motion-1] and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Updated Working Drafts of CSS Box Alignment and CSS Display Level 3
The CSS Working Group has published updated Working Drafts of CSS Box Alignment Level 3 and CSS Display Level 3. CSS Box Alignment Level 3 contains the features of CSS relating to the alignment of boxes within their containers in the various CSS box layout models (block, flexbox, grid, tables). CSS Display Level 3 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.
As we are wrapping up work on these specs in preparation for CR, most of the changes are fairly minor fixes and clarifications. A list of significant changes can be found in their respective Changes sections.
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] or [css-display]) 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 2017-07-19
- Resolved: Request updated PR for writing modes
- Resolved: Publish an updated WD of css-align
- Resolved: Drop
inline-list-item
- Resolved: Publish new WD of css-display
- Resolved: Accept this edit and close issue 1552 as resolved
- Resolved: Make the change to page up and down to put in intended direction and endpoint class
- Resolved: Take home and end out of intended direction class
- Resolved: Updated CR for scroll snap
- Resolved: Make the changes listed in issue 1436 in css2.1 and position
- Resolved: Accept the change in issue 1578:
object-fit: scale-down should become a flag
- The group discussed issue 1611: Should last-baseline’s fallback alignment be safe or unsafe?
- TabAtkins introduced the issue and indicated that they were leaning toward safe since it allows all the content to be reached.
- However, it was discovered on the call that the usual fallback is unsafe so using safe would cause unexpected behavior.
- There was value in both arguments, so discussion will continue on github in hopes of reaching a resolution next week.
Full Minutes
Minutes Telecon 2017-07-12
- Anyone with interest was asked to respond to the request for review from the TTML working group.
- fantasai will reply to Chris shortly in order to resolve if Writing Modes needs one more CR cycle.
- gregwhitworth began reviewing all the Flexbox tests to establish coverage.
- The group discussed how to continue moving CSS2 publications forward:
- Though the group recorded several resolutions in February to change the CSS2 publication process (recorded here) the new process still hadn’t been fully implemented. This has lead to there being greater confusion as to what is the most up to date and possibly new work occurring in more than one place.
- There was some concern that this new process was either not the best way forward or not well understood, so there will be a conversation at the Paris F2F to revisit the original decision.
- In order to reduce confusion as to what is currently out there, Bert will look through css-testing and make sure that any changes there are merged into css22 before deleting css-testing as well as css-source (which is currently empty).
- There were three items listed in github for the group to choose from to resolve the compatible alignments not always being compatible issue.
- Exclude items with
align-self: stretch and a specified height constraint (min-height/height/max-height) from align-content: last baseline alignment.
- Exclude items with
align-self: stretch whose specified height constraint gets triggered such that it no longer sizes as stretch.
- Treat items with
align-self: stretch and align-content: last baseline as having an end fallback alignment instead of a start fallback alignment.
- Resolved: Option 3 from issue.
Full Minutes
Minutes Telecon 2017-07-05
- Resolved: New WD of Motion Path
- Conversation around alias “nowrap” as “no-wrap” started with the three options the topic had previously narrowed down to:
- No change at all
- Add dashed version as a parse-time alias
- Add dashed version as a new values that behaves the same as nowrap
- The group was divided on if the change was a good idea so conversation mostly focused on option 1 vs either 2 or 3. There was very little interest to implement the change quickly or at all from vendors so it was decided to close this for now and let the advocates see if they can convince anyone else of the need.
- Resolved: No change for issue about adding no-wrap
- The group did some on the call test cases that showed there wasn’t currently any interop on computed value of a negative calc unit. birtles brought up some concerns around Animations that needed further consideration before a decision is reached. Discussion will continue on github.
- Resolved: trim white space before / after property value in a declaration.
- Resolved: New Values boilerplate language accepted.
- There was no one strongly championing the gradients with a single color stop proposal, so it will stay out of the spec until it finds an advocate.
Full Minutes
Minutes Telecon 2017-06-28
- Rossen will confirm if Writing Modes needs a CR publication before the PR request.
- Variables needs to republished after the tests are approved.
- Resolved: make “disc” not overridable.
- Resolved: adopt inset as the new positioning property name that’s used for shorthand
- fremy will create a poll with a description and diagrams to evaluate if inset is preferable over some of the other top options.
- Resolved: leave behavior as-is and not accept ‘legacy’ values for ‘place-items’.
- Resolved: accept the proposal that margin and position properties will return the specified values.
- Resolved: the baseline alignment in block direction of tables is not defined. Also add a note prompting implementors to bring back ideas if they have any.
- Resolved: leave the ‘left’ and ‘right’ values to fallback to start.
- Resolved: remove left and right from align-self and align-content in align L3.
- birtles gave a brief introduction to issue 1301 (reconsider name of
frames() timing function) in hopes of getting more discussion before next week’s call.
Full Minutes
Minutes Telecon 2017-06-21
- The open Values & Units topics will be prepared for discussion next week.
- There were three proposed options for issue 1317(Make selection change behavior configurable):
- no change
- change from current and make it so clicking in
user-select:none undoes current section
- have two values, one for each behavior
- Resolved: option 1: no change and add perhaps a non-normative note explaining adding this on the root isn’t a great pattern
- Resolved:
line-break: break-all on its own has the effect of allowing breaks everywhere
- This change will be put in L3 of CSS Text.
- Resolved: Columns do not clip by default
- Resolved: Columns are properties applied to block containers only.
- Those arguing in favor of the proposed alias of “nowrap” as “no-wrap” did so for author usability. However, the argument against the alias is that it adds weight to the API and sets a precedent for doing this again in the future. The two sides couldn’t agree within the time of the call so the topic was deferred back to github.
Full Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: