Minutes Telecon 2016-03-02
- Several people have requested more time to review the Snap Size ED before resolving on FPWD. Any questions will be discussed on the mailing list and, if the issues are resolved, the group will revisit in two weeks.
- Resolved: Accept #3 from the e-mail (Overflow is allowed visually, but it doesn’t project its “geometry” past the layout-contained ancestor, so it can’t trigger overflow past a layout-containment boundary) and say hit testing is currently undefined.
- Resolved: Mark the undefined hit testing as an issue.
- TabAtkins informed the working group that a decision was made by WHATWG to call
summary element a display list item and the disclosure is a list item. There was some strong objections to this decision; it was felt to be unfriendly to authors. Anyone who objects should contact WHATWG as it was their decision.
- Resolved: Remove the grid-template shorthand and fold it into the grid shorthand.
- TabAtkins will reach out to the appropriate implementors to continue conversation on FontFaceSet.
- The publication resolved on during Sapporo for CSS OM will happen soon.
Full Minutes
CSS Flexbox Level 1 Revision 1 Candidate Recommendation
The CSS Working Group has published an updated Candidate Recommendation of CSS Flexible Box Layout Module 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 horizontally and vertically within their container, and can “flex” their sizes and positions to respond to the available space.
This update closes the “Proposed Edited Candiate Recommendation” cycle of LCWDs, and puts Flexbox into the new W3C Process at the Candidate Recommendation level. A side-effect of this process has been to show the slowing rate of issues filed against Flexbox as the spec has matured (which allowed us to hit zero issues long enough to re-transition to CR).
Exact diff-marked changes, and their justifications, for the entire Candidate Recommendation revision cycle (since the original CR publication in 2012) are available in the changes section. A Disposition of Comments resulting in the latest set of changes (since the May 2015 publication) is also available.
As always, please send 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.)
Lots of thanks to the implementers who have been working with the spec, and with us, to improve the state of the spec together with their implementations. This module has not been easy to produce, and we are very grateful for their hard work, intelligence, and diligence in helping us build a new layout system for the Web!
(Note also that this spec is the first spec to be published with the new W3C specification style sheets. If you have comments on the new style, please file them at tr-design on GitHub or send them to spec-prod@w3.org or send them otherwise to fantasai.)
Minutes Telecon 2016-02-17
- An as-yet unnamed property will be added to CSS Images allow authors to indicate that higher quality rendering is desired. This will allow implementations of ‘auto’ more freedom in reducing quality to improve performance.
- The prose defining directional
angles as bearings will become a note stating that it is a CSS convention.
- Review was requested on
calc() serialization spec prose soon by those interested.
toggle() will move to level 4 of Values and Units- The group didn’t see a need to have image-rendering apply to gradients. Those with thoughts on this topic will also respond on the list.
- Generally the group was inclined to say that we allow visible overflow, but if it overflows the parent scroller you can’t see it. TabAtkins will discuss this decision with the implementor working on it to see if it fits with implementation experience.
- Resolved: Spec some set of
-webkit-user-select values.
- Rossen and/or gregwhitworth will help Florian decide what that set of values should be.
Full Minutes
Minutes Telecon 2016-01-27
- Resolved: Accept the new language as suggested in option B of this e-mail.
- There were still concerns about avoiding behavior that feels bad to a user when using 2D scrolling, especially when combined with mandatory.
- Resolved: Bring 2D snapping into the Snap Points spec and mark as at-risk.
- There were varied opinions on if there needs to be more terminology around the viewport to distinguish between different types.
- MaRakow reported he wasn’t blocked on this, so a decision wasn’t needed right away.
- It was agreed that the viewport terminology should be defined in device adapt, overflow, or the viewport specs.
- fantasai explained that she believed having
scroll-snap-padding and scroll-snap-margin physical and scroll-snap-align logical makes sense because scroll-snap-align interacts with the scrollers which operate in logical direction.
- MaRakow felt that her example case didn’t deal with the case when the user sets two properties on a 1D scroll. He’ll make another example case to further the conversation.
- The bikeshedding of the properties currently called
mandatory and proximity will happen at the F2F, but it was agreed that the names should be improved.
- The short conversation on splitting
scroll-snap-type seemed to indicate approval of the split, but naming will wait until the F2F.
Full Minutes
CSS Fragmentation L3: Candidate Recommendation
The CSS Working Group has published a Candidate Recommendation and invites implementations of CSS Fragmentation Module Level 3. This module describes the fragmentation model that partitions a flow into pages, columns, or regions and defines properties that control breaking. Changes since the last Working Draft are listed in the Changes section.
New since CSS Level 2:
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-break]) 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-01-20
- Resolved: Gaps between grid tracks are suppressed (always) at fragmentation breaks. Add note pointing out this is different from margins.
- Rossen will review the discussion on missing named lines search for Grid, but pending his review it looks good.
- Resolved: Rename
scroll-snap-area to scroll-snap-margin
- Resolved: If previously snapped, must resnap to that same snap position after content changes (if possible). If not snapped previously and now in range of a snap position, must snap.
- After the above resolution, there was concern about the second sentence.
- Resolved: The second sentence of the previous resolution is not precise enough.
Full Minutes
CSS Cascade 4: Candidate Recommendation
The CSS Working Group has published a Candidate Recommendation and invites implementations of CSS Cascading and Inheritance Level 4. This CSS module describes how to collate style rules and assign values to all properties on all elements by way of cascading (choosing a winning declaration among many) and inheritance (propagating values from parent to child).
Additions to Level 4 include:
There have been no changes since the September LCWD.
As always, please send any feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-cascade]) 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-01-13
- There was extensive discussion about the status of the snap points spec.
- MaRakow reported that he has been pushing updates to the spec and would be okay with publishing an updated working draft.
- TabAtkins felt that it was missing too many pieces to publish.
- TabAtkins proposed that the working group should resolve that the spec will go in the direction of the spec that TabAtkins and fantasai wrote, however MaRakow wasn’t comfortable with that until he had finished his full review.
- The suggestion to resolve was based on a desire to give implementers a clear indicator that snap points is going in the direction of their proposal and to ensure that any changes MaRakow made were documented. MaRakow offered to maintain a DoC or a change list to ensure that TabAtkins and fantasai can follow the changes.
- Instead of the resolution TabAtkins proposed, MaRakow offered to put a note at the top of the spec making it clear that it will be changing in the direction of the TabAtkins and fantasai document.
- TabAtkins suggested that other developers with experience in snap points help MaRakow do review to try and get the spec to publication by Sydney.
- Rossen also suggested that MaRakow, fantasai, and TabAtkins get on a call to work through the changes.
- Resolved: Add to the top of snap points “This spec is currently undergoing major changes in line with the resolutions here. During this process it is not safe to assume that the current form will be representative of what it will look like in the future. After the work in process is completed, it will closely resemble this proposal (link to Tab/Elika’s proposal)”
- Jihye and BradK reviewed their conversation about if it’s possible to merge the proposed center property and the polar-origin property.
- fantasai suggested that it may be possible to do everything in the center property using the already existing alignment properties. BradK will send fantasai a list of emails to review to catch up on the conversation so that she can reply with more details on her proposed solution after reviewing the use cases.
Full Minutes
Grid Layout Spec Workshops
Since the Flexbox workshops seemed to be helpful, fantasai is planning to organize a few Grid Layout spec workshops. There will be one in SF this month; add your availability to the Doodle if you’re interested. NYC and/or Philadelphia next month probably. And if neither of those work, you can get a group together to run one yourself—there are instructions for running a CSS spec workshop that anyone can organize.
Minutes Telecon 2016-01-06
- Resolved: Have the computed value for polar-angle keywords resolve to an angle
- Several people expressed support for
position: relative/absolute/fixed/sticky enabling the polar-* properties, but at least one implementor needed more time to investigate so the group will return to the topic, hopefully next week.
- The group needed BradK to be in the meeting to discuss the removal of
polar-origin in favor of his center proposal.
- MaRakow just came back from vacation today, but promised the group something to discuss about snap points for next week’s telecon.
- Resolved: Accept the new text for grid and multi-col changing the floor to a required amount. The new text is: “For the purpose of finding the number of auto-repeated tracks, the UA must floor the track size to a UA-specified value to avoid division by zero. It is suggested that this floor be ”1px” or less.”
- The potential options for how to drop repeated grid tracks with auto-fit came down to:
- Drop all empty columns
- Drop empty columns from either end
- Drop empty columns from end end.
- Several people were against 3 because it removed the symmetry of the property.
- The group didn’t have a preference between 1 and 2, so decided to stay with 1 since that’s what’s in the spec now.
- Resolved: Change the initial value of
align-content to stretch
- There’s still no final location for the May F2F.
Full Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: