CSS Flexbox Level 1 Update, Call for Comments
The CSS Working Group has published an updated Last Call of CSS Flexible Box Layout Level 1 to fold in feedback from the last LCWD. 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, mostly to fix various errors reported against the last draft. As before, 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 previous Last Call Working Draft and 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 11 June 2015.
We are particularly looking for feedback from authors on the percentage margins issue, and will accept comments posted through that post on CSS3.info.
And as usual, we will welcome and track any 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.)
Minutes Telecon 2015-05-13
- Anyone planning to attend the NYC F2F needs to make sure their name is on the wiki so that they can have a badge and wifi access. There are also directions on the wiki for how to get to the meeting. The agenda is light on topics, so everyone is encouraged to add items.
- Resolved: Publish a new LC of Flexbox
- Resolved:
stretch and auto compute to flex-start on items with display: flex
- Resolved: Accept TabAtkins proposal for Display (available here with further explanation here)
- Resolved: Accept proposal to allow multiple dots in grid template areas
- Resolved: Switch from parenthesis to brackets for grid line names
- The bikeshedding on renaming default will occur during the NYC F2F with all the suggestions being gathered for that discussion.
- The specs that are pending publication should start being published soon since ChrisL has worked out most of the problems that were holding them up. Once publication happens, CSS3 UI will need review since the authors want to go to CR in six weeks.
- The work on styling DOM ranges likely belongs as a part of the next level of CSS Pseudo and therefore shepazu will work with fantasai offline to integrate it.
Full Minutes
Minutes Telecon 2015-05-06
- Resolved: Accept the behavior of
document.scrollingElement but add more definition
- Resolved: Publish an updated working draft of CSS UI 3 with the additional section from tantek
- Resolved:
justify-content: stretch computes to stretch but behaves like start
- Note: this resolution might not have been recorded correctly. Please see member only discussion regarding potential clarification, available here.
- Resolved: Remove
position: center from Positioned Layout
- Resolved: Republish Positioned Layout without
position: page. Also update the short name.
- Conversation will continue on the mailing list to put together a case for re-introducing
position: page and it will likely become a F2F topic in NYC.
- Resolved: Don’t have
user-modify in CSS UI 4
Full Minutes
Flexbox and Grid Percentage Margins: Feedback Needed
The CSS Working Group has reached an impasse on the issue of percentage margins (and padding) in flex and grid layout, and needs your input to help decide it.
Option 1: Flex and grid items resolve percentages in margin-top and margin-bottom against the height of the element’s containing block.
Option 2: Flex and grid items resolve percentages in margin-top and margin-bottom against the width of the element’s containing block.
Option 1 makes vertical margins consistent with horizontal margins (which resolve percentages against the width of the element’s containing block). This is a theoretically simpler model, and works well with Flexbox and Grid’s dimension-agnostic layout concepts. However, it is inconsistent with CSS block layout, and causes the margins to collapse to zero when used in an auto-height container.
Option 2 is consistent with the behavior of vertical margins in block and table layout. It has usable behavior in auto-height boxes, and enables the “aspect ratio hack”. However, it is a less obvious behavior, and means the layout interactions change based on whether a flexbox is “row” or “column”.
(For more background, see discussion on www-style.)
We’re looking for comments from authors explaining which behavior they think is better for Flex and Grid layout, and why. Do you have use-cases that can only be achieved with one behavior or the other? Show us in a comment on CSS3.info!
Minutes Telecon 2015-04-29
- Rossen confirmed that the Houdini task force would be meeting 28 and 29 August after the CSS F2F hosted by Mozilla. If anyone is planning on attending, please add their information to the wiki.
- Most of the group was supportive of an exploration of the relationship between flexbox and rounded displays. It was agreed that this didn’t belong in level 1 of flexbox, but should instead exist as an exploratory section of the rounded displays spec and/or a wiki and mailing list thread with the conclusions potentially being integrated into flexbox 2.
- Resolved: In media queries, use boolean maybe semantics to handle unsupported syntax, i.e. false and unknown = false. (Re-evaluate if this ends up with back-compat problems.)
- Resolved: No animation events when subtrees are destroyed.
- Resolved: Start a next level of transitions with dbaron as an editor
- Resolved: Drop
/deep/ from dynamic profile and record an issue about keeping it in the static profile
- Resolved: Do layout containment, split containment into three pieces as per TabAtkins’ proposal and have
overflow: clip
- It was agreed that the coordinate systems need to be better defined, but that the definition belongs in CSS Image. The CSS Image authors will do more research and create edits to the spec and CSS 3 UI will reference CSS Image.
Full Minutes
Minutes Telecon 2015-04-22
- Everyone was encouraged to read the email from Florian outlining the different implementations and possible solutions for pre-wrap and white space processing. Discussion will continue on the mailing list and this will possibly become a F2F topic in May.
- Resolved: New Editor’s Draft for the next level of multi-column layout
- Resolved: Add just Florian as editor for this new editor’s draft for the time being
- The grammar for
media-condition will be changed to avoid requiring looking ahead by an unbounded amount.
- TabAtkins and Florian came up with the right behavior set for
@media not (unsupported-media-feature) vs @media not (unsupported+syntax), but it’s different from previous proposals, so they’ll contribute their new idea to the mailing list for further discussion/objections before hopefully getting resolution next week.
- TabAtkins and Florian came up with a proposal to address custom media queries before an
@import and will write the proposal for the mailing list.
- Resolved: Font MIME type registration is out-of-scope for CSSWG, FontsWG has a (partial) list, forwarding issue to them
- Resolved: Add that people may support larger Hebrew counters if they want
- Resolved: Re-publish Counter Styles CR with the above addition
- The addition of a
::flex-line pseudo-element might be good for a future level of flexbox, but not for the current level.
- Consensus was that renaming the global default was the least-bad option for dealing with the
cursor: default naming conflict and the name bikeshedding will happen on the mailing list.
Full Minutes
Minutes Telecon 2015-04-15
- Anyone planning on or interested in attending the CSS Houdini F2F in conjunction with the August F2F was asked to please contribute to the email thread planning dates.
- Resolved: Rename
fast and slow profiles to static and dynamic
- For now, conversation on the Selectors 4 matching algorithm will continue on the mailing list to allow more space to explain the complex algorithm and its relationship with the work being done on CSS Scoping.
- There was some disagreement as to if all
text-transform should be removed from a plain-text copy/paste or if there are some worth maintaining. People also disagreed on what behavior would be viewed as a bug by users. fantasai will reach out to the editing taskforce to get their feedback and use that to inform how the existing spec should be written and if there’s a need to create a spec to just address copy/paste issues.
- There was disagreement on the approach to and need for adopting user-select in CSS UI 4
- The
auto and none values for the appearance property in CSS UI 4 were agreed upon, but there was a lot of resistance to the button value. For now, Florian will move the button value to a note describing how the appearance property could later be extended if desired.
- Resolved: Accept
auto and none, do research on the rest.
Full Minutes
Minutes Telecon 2015-04-01
- The working group will request to meet on Monday and Tuesday during TPAC
- Resolved: New working draft of CSS 3 UI, accepting changes to
box-sizing
- Resolved: Then publish another working draft of CSS 3 UI.
- Resolved: Motion Path FPWD granted
- Resolved: Accept feedback coming from mailing-list as WG review of the WebVTT proposal
- A decision on the text change to Media Queries 4 will wait another week for Microsoft to continue reviewing.
- Discussion will also wait on changing required cursor image formats until next week to give Microsoft another week to review.
- Resolved: Add the
::marker { font-variant: tabular-nums; } rule to the default stylesheet
- Discussion of intrinsic sizes and multicolumn elements will continue on the mailing list and wait until next week when someone from Chrome is on the telecon.
- Resolved: Accept Myles’ proposal to make baseline of overflow non-visible inline blocks the higher of the actual baseline (at initial scroll position) and the margin-box bottom. Separately investigate whether to switch from margin-box bottom to padding-box bottom for sanity. (requries web-compat check)
Full Minutes
Minutes Telecon 2015-04-08
- There was disagreement as to if the specific order of state changes when loading fonts is needed to prevent bugs or if it’s an unnecessary step that slows performance. TabAtkins will gather more cases and the e-mails that led him to make the language more strict in order to further the conversation.
- Resolved: Change the appropriate sentence in Media Queries 4 to “User agents must re-evaluate media queries in response to changes in the user environment that they’re aware of”
- Resolved: Remove the timeout portions from the proposed font loading control spec.
- Resolved: Move Font Loading Control to the Font Loading spec.
- Resolved: We are recommending informatively
.cur support. Normatively must support PNG and SVG and saying should support animated formats too.
- Resolved: Accept fantasai’s proposal to add
text-combine-upright to ::marker.
Full Minutes
New Extended Units and Gradients Draft
The CSS Working Group is pleased to announce a new Editor’s Draft of CSS Expressive Generalizations and Gadgetry Level 1 (renaming suggestions welcome). This new module adds:
We are currently debating the publication of an FPWD. If you have comments, please contribute to the discussion on www-style!
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: