Minutes Telecon 2014-05-07
- Resolved: Publish an update Working Draft for Grid
- When discussing handling whitespace in
calc() there was basic agreement that when dealing with + the added whitespace wasn’t needed, but there were concerns about – being confused with keywords. There was agreement that the priority should be author readability/usability not tokenization. TabAtkins will outline the exact proposal on the mailing list to solicit feedback with a goal of doing a poll of the working group on the next call (14 May)
- Resolved: Publish updated Working Draft of GCPM
- The new GCPM Working Draft will maintain references to the items that were removed and what specs those items landed in.
- Resolved: Add
:modal to Selectors level 4
- There was some concern that a pseudo-class wasn’t the best way to address
:modal, but not enough to block a resolution.
- A few members of the group expressed an interest in eventually investigating and potentially creating a pseudo-class to query properties.
- The Flexbox editors asked for anyone with comments to submit them ASAP so that they can publish a new Last Call next week in order to garner input on the two different algorithms for resolving lengths.
- Everyone was again reminded to add discussion topics for the Seoul F2F to the wiki.
- Resolved: Add fantasai and dauwhe as editors to Line Layout
Full Minutes
CSS Custom Properties for Cascading Variables LCWD updated!
The CSS Working Group has published an updated Last Call Working Draft of CSS Custom Properties for Cascading Variables (colloquially known as “CSS Variables”). This specification defines custom properties, which are author-defined properties which can accept any value, and the var() function, which lets authors substitute the value of a custom property into another property.
This new Last Call draft has been published because there have been significant changes to the syntax of custom properties and how they are used in the var() function—rather than defining custom properties with names like “var-foo”, they now have names like “–foo”, to be consistent with the plan for other custom extensions to CSS. The CSSVariablesMap interface has also been dropped, in the expectation that a future module extending the concept of custom properties will define something more useful.
Changes since the last Working Draft are listed in the Changes section.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-variables]) 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 2014-04-30
- Plh plans to send the charter in by the end of the week.
- Resolved: Change
mask-box to mask-border in Masking
- Krit and fantasai brought the group’s attention to the changes made to Masking and asked for review before a decision on going to Last Call.
- There was a lot of concern about the proposal to split Text into smaller pieces since they are highly related. A few potential smaller splits were discussed and a look into what pieces were holding the spec up most was advised. The details of a potential split was declared to be perfect for a F2F conversation.
- Resolved: No change to
calc() in Media Queries
- Due to the lack of immediate concern, the Box model/Render tree conversation was declared another great F2F topic.
- There was some concern about it not being easy to standardize atomic inlines. Fantasai will come up with some proposed text.
- The conversations about changing MediaQueryList to use events and scrollbar stickiness will both stay on the mailing list for now.
- There was a request for more time to read up about the proposal to add
any-pointer and any-hover to Media Queries. MaRakow and TabAtkins will discuss technical details about the proposal on the mailing list.
- TabAtkins stated that he needs to go back to his text about officially using the behavior of ‘animation’ with regards to parsing
custom-idents in properties and come up with another draft before consideration.
- WG members were reminded to add discussion topics for the Seoul F2F to the wiki. Anyone that hasn’t already reserved their hotel room should do so ASAP.
- Resolved: New Last Call for Variables
- zcorpan drew attention to his e-mail revisiting
calc() and whitespace and requested review for discussion on next week’s call.
Full Minutes
First Public Working Draft of the CSS Will-Change Module Published
The CSS Working Group has published a First Public Working Draft of CSS Will-Change. This module defines a single property, “will-change”, which allows the author to provide hints to the browser about what aspects of an element will change in the near future, allowing browsers to set up appropriate optimizations ahead of time, before the change occurs.
Implementation is already proceeding in Firefox and Blink-based browsers (Chrome, Opera), and this specification is expected to advanced to Candidate Recommendation quickly. Any nitpicks on the precise semantics of the property are welcome.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-will-change]) 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 2014-04-23
- fantasai requested more attention to the Backgrounds and Borders change in spread-radius including some assistance writing a document to illustrate the changes.
- Resolved: FPWD of Non-element Selectors
- The group expressed a desire to have a level number added to the name, though what number it should be will decided on the mailing list.
- The group inquired about the specifics of how division by infinity would be handled based on this proposal to Values and Units. There was also a lot of uncertainty about if the sign of 0 should be tracked. It was felt that since current behavior creates a parsing error, no changes needed to be made to level 3.
- Resolved: Add calc() algebra to level 4 and keep an issue in there about +0/-0 handling
- Conversation about subgrid will stay on the mailing list.
- When discussing a request to reconsider handling of percentage margins/padding, Tab expressed a desire to keep grid and flexbox consistent, no matter the final decision. Rossen stated that Microsoft would have lots of backwards compatibly issues if the handling of grid was changed at this point.
- Resolved: Keep current behavior where percent vertical padding/margins resolve against height
- It was felt that what the current flexbox spec said should happen to item height when max-height was applied to a flex container was clear, but that the alternate Blink behavior was more desirable.
- Resolved: Change the spec’s (flexbox) max-height implementation to match Blink’s implementation
- Discussion on box model/render tree was deferred to next week.
- In conversation about the potential of a
:role() selector there was agreement about it being interesting and/or possible to work around the dependency issues with a pseudo-class matching ARIA roles, but discussion will continue on the mailing list.
- There wasn’t certainty that the last grammar combinator (proposed here) was needed, but exploration will continue. TabAtkins suggested a ?? combinator, which wasn’t adored. Other possibilities were brought up in IRC after the telecon ended.
Full Minutes
Minutes Telecon 2014-04-16
- Resolved: Default for CH unit is 0.5EM in Values and Units
- Resolved:
background-position-x/-y, background-repeat-x/-y approved for level 4 of Backgrounds and Borders.
background-size-x/-y was also discussed, but didn’t garner much support.
- Resolved: Make the
image() function always respect EXIF orientation metadata in Backgrounds.
- There were lots of questions about the implications about the proposed change to have MediaQueryList use events. The main issue was how a single event that would change multiple items would be handled. TabAtkins will bring this item to the mailing list for feedback.
- TabAtkins presented the idea for being able to position the scrollbar at a certain distance from the bottom once you scroll to the bottom of the content. There was discussion about the use cases for a property like this and the interplay between this proposed property and sticky positioning.
- Resolved: Discussion continues over e-mail
- Subgrid was deferred another week.
- The working group wasn’t against adding a pow operator to
calc() in Values and Units, but some people didn’t feel there were sufficient use cases. General feeling was that this is something that can be done in the future, but is not a priority.
Full Minutes
CSS Scoping, CSS Line Grid First Public Working Draft
The CSS WG has published First Public Working Drafts of two new modules:
- CSS Line Grid Module Level 1
- Contains CSS features for aligning content to a baseline grid.
- CSS Scoping Module Level 1
- Defines various scoping/encapsulation mechanisms for CSS, including scoped styles and the @scope rule, Shadow DOM
selectors, and page/region-based styling.
These are early-stage working drafts: the features described therein are not well-baked and may change dramatically or be removed. We’re soliciting comments on both design and details of these features, and implementers should participate in the design-level discussions happening on www-style before considering implementation.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-line-grid] or [css-scoping]) 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 2014-04-02
- Resolved: FPWD for
will-change.
- Resolved: FPWD for CSS Scoping
- Resolved: Modification of the validity of an unknown prefix in selectors and insertion of namespace rules.
- Fantasai expressed that she still believes moving
subgrid to level 2 of Grid would create accessibility issues that would be hard to rectify even after level 2 is released. TabAtkins stated that he still believes that the inclusion of subgrid in level 1 will cause too much of a delay to implement before shipping. The discussion will continue on the mailing list with sylvaing recommending a focus on use-cases instead of general speculation on what adopters may or may not do.
- Resolved: Use percentage values for key arguments and map from/to keywords to 0% and 100% respectively in Animations.
- Resolved: Keytext on setting invalid value should throw an error in Animations.
- The various other Animations questions concerning
keyframes all revolved around reaching consensus on how browsers implement the spec. Sylvaing will solicit feedback from the browsers to ascertain the best path to compatibility and then move to solve the other issues.
- It was agreed that global keywords should be excluded as
custom-ident values, but there still isn’t a clear path on how to decide what other keywords should be excluded. Discussion will continue on the mailing list.
- Resolved: Add q unit to Values and Units.
Full Minutes
CSS Flexbox Level 1 Revision 1 Last Call for Comments
The CSS Working Group has published a Last Call of CSS Flexible Box Layout Level 1 in order to gather feedback on recent changes. 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 to fix various problems, particularly in the layout algorithm, found through implementation review and experience during the Candidate Recommendation phase. 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 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 22 April 2014: please either send comments by then, or request an extension.
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.)
Minutes Telecon 2014-03-26
- Glazou asked that those that volunteered to speak at the event with the Korean government following the Seoul F2F message him with proposed topics.
- Resolved: Rename to extent and measure
block-size and inline-size in Writing Modes.
- TabAtkins and fantasai discussed the proposed agreement that they came to for combinators and pseudo-elements in Shadow DOM. They also brought to the group their proposal for CSS Scoping which includes their above solution, some styling text from Regions, and new proposed syntax of
@scope.
- Resolved: Editor’s Draft for CSS Scoping.
- Granting a FPWD for CSS Scoping will be considered at next week’s telecon after the potential issues are integrated into the document.
- Specific details on how the group will handle asynchronous decision making was decided:
- All requests will go through the co-chairs.
- Co-chairs will post the request for decision on both the www-style list and the internal working group list as well as the twitter account.
- Most decisions will be given at least a week for comments with urgent and administrative decisions potentially being given shorter periods.
- The group agreed in principle with twk’s proposal for CSS Ruby being in line with HTML5′s treatment. fantasai will look specifically at fixing the spec.
- dbaron’s question about handling how style changes interrupt an already-running transition and put it on a different path was discussed with Google’s implementor being willing to help him come up with a solution.
- Resolved: Move to matrix for the serialization of the computed value for Transitions.
Full Minutes
![[Photo: group photo of the CSS working group in Lyon, France]](/web/20140509181442im_/http://www.w3.org/Style/CSS/csswg-2010.jpg)
Contact: