Minutes Seoul F2F Part II: 2014-05-19 PM – Values and Units, Counter Styles, CSS Formatting for Books, Font Load Events, Future F2F Meetings, CSS Syntax Unpaired Surrogates, MQ Listener
Values and Units
- Resolved: Any new properties with a custom-ident, make them positionally unambiguous.
- Resolved: We handle the list-style custom-ident in the fashion of Animation.
- Resolved: Use
[a? b?]! for the one+ in-order grammar
- Resolved: Publish an update of Values and Units
Full Minutes || Spec Referenced
Counter Styles
- Resolved: Add “speak this as a word” value to
@counter-style speak-as.
- Resolved: Change
@counter-style‘s speak-as descriptor values to bullets, numbers, words, and spell-out.
- Resolved: Process pad before negative (so that we get -02, -01, 00, 01, 02)
- Resolved: The spacing between a list item and its content should be done as space characters in the suffix.
- Resolved: Change the name of
override to extends
- Resolved: Publish a 6 week last call of Counter Styles
Full Minutes || Spec Referenced
CSS for Formatting Books
Full Minutes
Font Load Events to LC
- Resolved: Publish LC for font loading, with change/note about
SetClass dep.
Full Minutes || Spec Referenced
Future F2F Meetings
- The next F2F will be 8 September to 10 September somewhere in Europe with the site TBA.
- The meeting after TPAC will be in early February with a lot of possible site suggestions include a few options in the US and Australia.
Full Minutes
CSS Syntax – unpaired surrogates
- The potential issue of unpaired surrogates coming in from JS will be left with no change.
Full Minutes || Spec Referenced
MQ Listener
- Resolved: Make
MQ lists and EventTarget for the change event and alias the existing listener to addEventListener and removeEventListener
Full Minutes || Spec Referenced
Minutes Seoul F2F Part I: 2014-05-19 AM- Flexbox, Transitions and Animations, calc(), Image Values 3
Flexbox
- Resolved: Close issue on whether
flex-basis: auto should resolve at computed value time. Clarify that the flex-basis: auto flips to width/height at used value time.
- The flex resolution algorithm has been redrafted since the LCWD to be closer to the structure of the earlier CR draft while preserving the changes to handle flex values continuously approaching zero. (Various technical errors reported in the LCWD have also been fixed.) The editors are requesting review from those interested.
- Some concerns about handling the static positions of absolutely-positioned child of were discussed:
- The group basically agreed to switch the flexbox/grid static position model to match a 0x0 static position placeholder box, but then also define that, depending on the alignment properties, the abspos child aligns relative to its static position differently.
- This should give the same layout results as what’s in the spec right now.
- A final resolution was held off until a decision could be made if the start point should be a box or a point.
Full Minutes || Spec Referenced
Transitions and Animations
- For transitions, dbaron stated that there was only one major issue to be addressed before last call: how to handle when a transition starts/stops
- This is a major issue, however, and will require a dedication of time.
- Current hope is to be able to address it in June
- For animations, dbaron stated that there was a lack of editorial resources to allow the spec to progress. Several people were suggested as being worth approaching for editorial help.
- Shane discussed his work creating a cohesive approach to transitions, animations, and web animations which he intends to be the foundation of transitions/animations 4.
- Resolved: Migrate Shane’s document (http://rawgit.com/shans/98cb810920ac43876020/raw/b77db7529411066c9f3cdd36a52d0b98553525f9/Overview.html) into the dev pages and the SotD section should say that it’s intended to be incorporated into Transitions and Animations 4.
Full Minutes || Specs Referenced: Transitions, Animations
calc()
- The issue of whitespace in
calc() was addressed.
- The group agreed that there was no way to completely eliminate whitespace requirements, instead only being able to limit the instances of required whitespace. This lead the conversation toward what was easier for authors – getting close to the ideal of no whitespace or sticking with existing easy to remember, though non-ideal, whitespace rules.
- Resolved: No change to
calc() whitespace rules
Full Minutes || Spec Referenced
Image Values 3
- The two disparate types of image fallback were addressed with the group expressing strong support for fallback to a color, but wishing to simplify image fallback.
- Resolved: Drop fallback from image except fallback to color. Later we introduce that fallback as an explicit function.
- Resolved: Cut out everything not defined for image-orientation, remove additions, move it to an appendix, call it obsolete and make a custom CR exit criteria stating it doesn’t need to be tested to exit CR.
- Resolved: Specs that define obsolete features don’t need to test those features to exit CR.
- Of the possible solutions for non-square pixels, the group leaned toward deferring to HTML’s handling of video.
- TabAtkins plans on bringing requesting a LC for Image Values 3 on the first telecon after the meeting.
Full Minutes || Spec Referenced
Updated Last Call Working Draft of CSS Masking Level 1 published
The CSS Working Group and the SVG Working Group have published an updated Last Call Working Draft of CSS Masking Level 1. CSS Masking provides two means for partially or fully hiding portions of visual elements: masking and clipping.
- Renamed mask-box* properties and terms to mask-border*.
- Added support for multiple mask layers. (Similar to multiple background layers for background.)
- Added the mask-composite property to control compositing of multiple mask layer images with the keywords add, subtract, intersect and exclude.
Changes since the last Working Draft are listed in the Changes since last publication.
Please send feedback to the (archived) public mailing list
public-fx@w3.org
with the spec code ([css-masking])
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 the module Geometry Interfaces published
The CSS Working Group and the SVG Working Group have published a First Public Working Draft of Geometry Interfaces. This specification provides basic geometric interfaces such as DOMPoint, DOMRect, DOMQuad or DOMMatrix used by other modules or specifications.
Implementation is already proceeding in Firefox and prefixed implementations are shipping in Safari, Chrome, Opera and Internet Explorer.
Please send feedback to the (archived) public mailing list public-fx@w3.org with the spec code ([geometry]) 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-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
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: