CSS Flexbox CR Updated
The CSS Working Group has published an updated Candidate Recommendation of CSS Flexible Box Layout Level 1. 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. We expect this model to be particularly useful for UI layouts.
This update addresses issues found since the 1 March 2016 publication. Exact diff-marked changes, and their justifications,
are available in the changes section. A Disposition of Comments resulting in the latest changes is
also available.
Please send feedback by either filing an issue in GitHub or sending mail 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 2016-05-25
- Resolved: The grid-template and grid-gap properties have no effect on a sub-grid.
- Tentatively the group resolved that auto-repeat should be invalid despite existing implementations. And remove the grammar that allows
repeat for columns as it was an accident.
- If there are no objections on the mailing list before the next telecon, the group will formally resolve.
- TabAtkins asked anyone interested in the grid algorithm to review section 12.1, issue #8
- Resolved: Take the clamping behavior for error cases on subgrid where items are outside the subgrid (issue 4).
- Resolved: Add
overflow-wrap: break-spaces to level 3 of text
- TabAtkins brought to the group that the spec and implementations disagree on behavior for when a scroll container with overflow auto or scroll and padding on all sides: does the padding on the end edges get included in scrollable area?
- In the block direction some implementations do show padding and it was generally agreed that that is the author expectation.
- There was a lot of concern in changes breaking web compat, especially in the inline direction as no specs do that.
- TabAtkins proposed amending the spec to say that padding should be respected in the block direction and noting the issue around the inline direction which would encourage people to note breaking behavior around that or make test implementations allowing it.
- Conversation will continue on the mailing list.
- Resolved: Publish a new WD for Overflow
Full Minutes
CSS Grid Layout – Updated Working Draft
The CSS Working Group has published an updated Working Draft of CSS Grid Layout Module Level 1. This module defines a new type of layout manager, the grid, which makes it extremely easy to specify complex, responsive 2-dimensional layouts for a page or components.
This new draft incorporates a lot of feedback since the previous draft, including a simplified subgrid proposal, a much-improved grid shorthand syntax that accommodates auto-flow grids, and many bugfixes. Changes since the last Working Draft are listed in the Changes section, and a Disposition of Comments is available.
Please send feedback by either filing an issue in GitHub or sending mail 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.)
We do expect to transition this module to Candidate Recommendation shortly, so any feedback had best be sent ASAP!
CSS Box Alignment Level 3 – Updated Working Draft
The CSS Working Group has published an updated Working Draft of CSS Box Alignment Level 3. This module defines new features 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.
This draft includes a slew of relatively minor tweaks and bugfixes, particularly to the baseline-alignment section, plus a change in the default “safety” of overflow handling. Changes since the last Working Draft are listed in the Changes section.
Please send feedback by either filing an issue in GitHub or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-align]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
We would also welcome the donation of any illustrations or examples, as this document desperately needs more.
Minutes Telecon 2016-05-04
- There was agreement on the mailing list that media queries should respond to page sizes set in @page, but Florian wanted more guidance with what direction the proposed text should take. Florian suggested that he could write the text to allow the property function similar to @viewport. There was some uncertainty as to if this was the right approach, though several people were also in favor of it. Florian will write proposed text including use cases and bring it back to the group.
- Resolved: Adopt the proposed convention for propdef tables for shorthands (available here).
- ‘proximity’ and ‘mandatory’ still need to be renamed in Snap Points, but the group didn’t like ‘strict’ and ‘loose’.
- In the naming conversation around snap alignment container, there were really three items that need to be named:
- a box that has a scrollbar
- the viewport of the scroll container
- the snapping area of the viewport of the scroll container (i.e. viewport minus scroll-snap-padding)
- Resolved: A div with overflow that’s not visible (A) is a ‘scroll container’
- Resolved: B (the viewport of the scroll container) is a scrollport. C (the snapping area of the viewport of the scroll container) is a snapport.
Full Minutes
Minutes Telecon 2016-04-27
- Resolved: When a range endpoint falls in the middle of a grapheme cluster,
Range.getClientRects() should include the entire grapheme cluster.
- gregwhitworth asked for updates on browsers for their status on the control characters change resolved in Sydney in 2015.
- Safari hasn’t begun implementation
- No one on the call could speak for the Chrome team.
- The conversation around
viewport-fit for setting the viewport in the non-rectangular display will be postponed to the F2F where a whiteboard is available.
- The terminology will also need to be decided on to make the concepts clearer.
- The ‘auto’ value of
viewport-fit as written in the spec wouldn’t be useful. There was wide support for an ‘auto’ value that says do something between contain and cover that’s smart if you want to or just do contain. This would allow UAs to innovate in this new space.
- Changing the initial value of
polar-anchor to ‘auto’ brought up two different models of how polar-anchor should be used. There wasn’t enough time to decide between the two, so the conversation will continue either on the next telecon or the F2F.
- Either model would be fine with the initial value being ‘center’ so that is likely to stay the same no matter the result of the conversation.
Full Minutes
Minutes Telecon 2016-04-13
- The test submission process is being reviewed in hopes of making the tests more useful to more people.
- The discussion began around where on the spectrum from the current metadata status and no metadata should the working group land.
- It was expressed that the first step should be remove the pieces everyone agrees should be removed and see how much progress can be made.
- Tests should be accepted if they contain the important metadata, even if some of the styling is off with a request to fix the problems on the next bug.
- From there, the conversation moved to the build system being another thing obstructing tests.
- There was general agreement that the build system as it stands now isn’t needed, though there will still need to be metadata left in to get which tests apply to which spec.
- gsnedders will do the work to remove the build system and see what progress that creates on testing.
- Discussion on testing will continue on the mailing list.
- Resolved: Add
viewport-fit: contain to Round Display spec
- The description of the
viewport-fit property will need to be clear about the order it occurs in with other properties.
- The group liked the idea of having an additional attribute returning shape of display, however this information isn’t currently exposed to the browser.
- Until the device shape information is available, Florian will continue working on the media feature he is building to return if a device is round.
- Bert will continue looking through the errata of CSS 2.2 for test coverage and report back to the group once he’s done.
- Resolved: Accept grid issue 26; adopt the language in option B on this e-mail.
Full Minutes
Minutes Sydney F2F 2016-02-03 Part II: SVG Text Issues, CSS Masking, Filters, Gradients & Dithering, Investigation about JS API for realizing Level of Details, Transitions and Animations, Matrices
SVG Text Issues
- The group went through a list of issues and problems that Tav has documented here.
- Discussed using exclusions to help handle SVG shapes
- It was noted that shape-inside doesn’t have an equivalent functionality to wrap-flow (which says which side of the shape to fill); this is needed to handle filling concave shapes
- Discussed ideas for sequentially filling shapes
- Need to clarify that line boxes are fitted to non-rectangular shapes by requiring zero intersection.
- Middle (half of the x height) and Alignment (synonym for text top and text bottom) baselines may be useful to add to CSS Inline.
- It may be preferable to have the baseline table reset when the baseline font changes – this would be a behavior change from SVG 1.1.orientation.
- A decision on default values for mathematical values will wait for more data.
Full Minutes
CSS Masking
- Resolved: Change ‘auto’ value of mask-mode to ‘match-source’.
- birtles will investigate dropping mask-type. If it’s not dropped, he will update the normative text.
Full Minutes || Spec Referenced
Filters
- The authors will keep moving the spec toward CR.
- Tav presented a new filter primitive he’d like added to level 2; dino agreed it was interesting and will look into adding it to the spec.
Full Minutes || Spec Referenced
Gradients & Dithering
- Either AmeliaBR or Tav will create a proposal to either offer author control or spec guidance for browsers on dithering.
Full Minutes
Investigation about JS API for realizing Level of Details
- stakagi presented some very detailed work he had done (Available here)
- His wiki will be linked to from the spec as a list of things the spec needs to address.
Full Minutes
Transitions and Animations
- Both specs are being worked on and dbaron expressed a desire to have help in making progress.
Full Minutes
Matrices
- zcorpan requested review of the edits he made (Available here) in the WHATWG geometry spec.
Full Minutes
Minutes Sydney F2F 2016-02-03 Part I: 2017 F2F Meetings, Scroll-linked Animations, Fill & Stroke on CSS Text
2017 F2F Meetings
- All possibilities were tentative, but the proposals were:
- January or February will be US or Europe
- Spring 2017 Japan
- Summer 2017 possibly TPAC, depending on TPAC’s timing
Full Minutes
Scroll-linked Animations
- Due to increased interest, the group revisited a demo that dino gave back in 2014 on how to handle scroll-linked animations.
- In the time since the demo, there has been in increase in usage of scroll-linked animations as well as the Houdini effort which may make it easier to support use cases.
- As an example, exact pull-to-refresh behavior is likely out of scope, but it can be made easier.
- There were several different aspects that need to be addressed in order to spec this.
- Should have triggers be pre-transform.
- Anchor points need to be carefully defined in order to prevent undesirable behavior.
- This may generally have performance issues but, like custom layout, authors will work out how to use it performantly.
- Parallax triggered animations will need to be supported.
- The group went through a list of scrolling use cases shane had prepared (available here)
- Dino will take his original e-mail and turn it into an explainer document.
Full Minutes || Spec Referenced
Fill & Stroke on CSS Text
Minutes Sydney F2F 2016-02-02 Part II: Behavior of contains:paint and overflow:clip, text-overflow and resize properties; CSS Text; Exclusions and bidi; Snap Points; bookmark-level: auto; Sizing
Behavior of contains:paint and overflow:clip, text-overflow and resize properties
- Resolved: Remove any mention of
overflow:clip from the containment spec and change section 3.3 to define that clipping happens (just not by affecting value of ‘overflow’)
Full Minutes || Spec Referenced
CSS Text
- Resolved: In order to prevent overflow or wrapping of invisible white space, spaces at the end of a line must either be visually collapsed to fit within the line or must hang outside the line (as in hanging punctuation)
- Resolved: Add
word-break: break-spaces
- Resolved: Drop
pre-wrap-auto
- Resolved:
text-wrap: balance evaluation works off of remaining space in the line, not average line length.
- The changes to text-decoration ( listed in this e-mail) need to be explained further before a resolution can be reached.
- Resolved: Add
word-break: break-word to spec if Edge/Firefox find it critical enough to Web compat to implement it.
Full Minutes || Spec Referenced
Exclusions and bidi
- Resolved: When a line is split by an exclusion, each side is its own line box for the purposes of bidi algorithm (i.e. they are effectively separated by a soft line wrap). Which line box is first depends on the block’s directionality.
Full Minutes || Spec Referenced
Snap Points
- Resolved: The only pseudo elements that snap points apply to are
::before/::after but add a note that suggest there “might” be a future pseudos that can support snap points.
- There needs to be more use cases before deciding how to behave with snapping to unreachable elements
- Still no decision on renaming proximity and mandatory. Current suggestions are near|always, force|allow, force|proximity, force|near or keep the original names.
- Resolved: Defer 2D snap to the next module level of snap points
Full Minutes || Spec Referenced
bookmark-level: auto
bookmark-level will stay the same in CSS Break.
Full Minutes || Spec Referenced
Sizing
- gregwhitworth will investigate if min-width on tables is possible.
Full Minutes || Spec Referenced
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: