Minutes Telecon 2017-01-04
- The group was reminded to add topics to the wiki for next week’s F2F. Also, the wiki for the Tokyo F2F is up.
- Resolved: Accept the proposal explained here.
- The proposal to address implied minimum size for grid items hasn’t been reviewed enough yet and will be moved to the F2F agenda.
- Resolved: Re-publish Scroll Snap CR with these changes.
- Resolved: Make the change to speak value properties (to
auto|always|none) and inform the a11y TF.
- There is a possibility this resolution will need to be reversed because it was discovered later that webkit does already implement the speak property.
- Having the auto value of speak also respond to the visibility property needs feedback from the a11y task force and from more people in the a11y community to ensure this change would be beneficial for everyone as there is a wide variety of reasons for using the speak property.
- The group reviewed the two proposed approaches for maintaining CSS2 (available here). A third approach was discovered over the call to have a Note that contains the items the WG has agreed to, but are not ready to pass the PR criteria and be in the PR CSS2.1 spec. There were still concerns over how comments will be made and tracked on these two specs that weren’t addressed by any of the proposals. The group ran out of time on the call to reach a conclusion so this topic will be added to the F2F agenda. Also, fantasai will send a summary to the mailing list.
Full Minutes
Minutes Telecon 2016-12-21
- Will-change, Variables, and Flexbox were mentioned as specs that should move to a higher status in the 2016 snapshot.
- ChrisL will prepare a list of specs not mentioned in the 2015 snapshot to help the group discover any specs that should be included in 2016.
- The proposal on how to address stretching grid items in both directions is summarized in the github issue. Anyone interested, especially from the design/webdev community, was asked to review before the next call (4 Jan).
- Similarly, the proposal to correct the language around implied minimum size is summarized on github and edited into the spec. A resolution will be sought on the next call.
- Resolved: Accept proposal from TabAtkins and fantasai in issue 767
- Resolved: Make color properties return used value as resolved value
- The ‘Overflow: Consider support for overlay scrollbars’ topic (available here) will be added to the F2F agenda and was renamed to ‘Consider reserving space for scrollbars with some property’ to avoid confusion.
- There was general support in formally specifying a feature like
-ms-scroll-chaining, but it wasn’t ready for a resolution. The latching behavior done by webkit and Chrome should be added to the proposal or at least able to be done with the properties. It was agreed that the name will need to be improved. This will be added to the F2F agenda.
- Resolved: Ink skipping applies to overline and underline, but not line-throughs
Full Minutes
Minutes Telecon 2016-12-14
- It is still undecided if there will be a meeting next week.
- A location is being sought to host a summer F2F in Europe. There’s also a doodle for members to add availability information.
- Resolved: No change in current custom properties for issue #757. Need to solve this issue with future work.
- Resolved: We drop the implicit requirement that selectors parsing remains LR1 and as a consequence we remove specialized selectors from the syntax and replace accordingly.
- Resolved: Do not add device-pixel-ratio unprefixed.
- It was left undecided if
-webkit-device-pixel-ratio should be defined in the Media Queries spec. Several people had no wish to define it since it’s an alias to the resolution media query, but there was concern that that’s compatibility hostile since currently you need -webkit-device-pixel-ratio to be web compatible.
Full Minutes
Minutes Telecon 2016-12-07
- The F2F meeting in Japan is confirmed for 17-21 April.
- The telecon on 28 December is canceled. 21 December and 4 January are currently planned to occur, but members should keep an eye on the private list.
- The specs that were a part of the FXTF are now the sole responsibility of the CSSWG. Rossen will investigate the best way to move the specs in the CSSWG drafts & github repo making sure to preserve spec history and issues.
- There were two options for how to address when an image is stretch in one direction and has a value like center in the other direction.
- It always preserves aspect ratio
- Ignore/break aspect ratio
- There was no clear consensus between the two options. A few people felt that the problem is created by putting sizing in an alignment property and there should be thought on avoiding that. The interested parties will talk over github and maybe get on a call to keep thinking through the implications of these issues.
- There were two views on the relative URL resolution in var() references issue:
- This is an edge case and an exception shouldn’t be made as it’s harder to teach exceptions
- This problem makes URL in variables close to useless and therefore needs fixing
- Several vendors weren’t giving options and TabAtkins, who had strong options, wasn’t on the call, so discussion will continue on github and a resolution will be sought on next week’s call.
- Resolved: Add a note along the lines of koji’s example telling authors how to work around the lack of correct implementation. (In reference to the proposal to replace “‘text-orientation: upright’ to cause strong LTR” with author notes how to do it)
- This section will remain as a MUST with a plan to argue it’s an edge case and shouldn’t block a move to PR.
Full Minutes
Minutes Telecon 2016-11-30
- gsnedders and gregwhitworth offered to review the test suite for CSS 2.2. Anyone with interest in a section of CSS 2.2 was also asked to review at least that section. In addition, anyone with interest was asked to review the edits made to CSS 2.2.
- fantasai will start a thread on the member e-mail list to discuss how best to keep the CSS 2.X specs updated quickly as items become interoperability implemented.
- For CSS 2.2 individuals should put issues in where they think there should be a link to another spec. In CSS 2.3 there will be work done to integrate all relevant links.
- The group agreed to a goal of getting CSS 2.2 to CR within a week after the Seattle F2F. Review requests will be sent to the appropriate groups noting that are errata only to help them prioritize.
- Rossen & TabAtkins agreed to review the conversation on github around the new definition for ‘normal’
- Resolved: For all layout modes when you’re figuring out static position of an abspos child treat auto margins as 0 regardless of normal positioning rules.
- Everyone agreed that the proposed edits for computed value of currentColor should occur, but Florian will bring his proposed text to the group as there are many specs that will need changes.
- Resolved: Change the applies to line to all elements
- Resolved: Add an informative note as to what is a caret and what is not.
Full Minutes
Minutes Telecon 2016-11-23
- Anyone with interest was asked to respond to the review request for TTML2.
- fantasai wasn’t ready to discuss the remaining grid issues yet so the conversation will continue in hopes of being able to come to the group for resolution next week.
- Resolved: Rename
offset-rotation to be offset-rotate
- TabAktins was actioned to confirm this change is okay with Blink since no one was on the call to speak for them.
- Resolved:
mask-mode can be anywhere in the mask shorthand other than between position and size
- There were concerns that adding the slash to the shorthands of alignment properties created an inconsistency with other established properties such as in background-position. On the other hand, there was a feeling that the slash would be intuitive to those that use grid and flexbox and that not having the slash creates a bad precedent.
- Resolved: Don’t add the slashes (to the alignment property shorthands).
- The group moved on to discussing what would be needed to move Align to CR since there are dependencies for Grid. fantasai proposed trimming the spec to have only single-keyword values only for longhands in this level of Align and moving the rest to the next level. These properties are derived from Flexbox and are therefore stable and unlikely to change. dbaron expressed a desire to know what is already shipping in browsers before removing items from the spec so discussion will continue next week once there’s a fuller picture of what’s shipping.
Full Minutes
Minutes Telecon 2016-11-16
- Resolved: initial-letter and ruby is explicitly undefined.
- dauwhe will incorporate this change into the spec.
- Resolved: Standardize on Edge behavior as described by dbaron in the issue.
- Rossen will incorporate this change into the spec.
- Resolved: Accept pull request from issue 713
- Resolved: Take pull request 714
- There was a discussion on what work is necessary to bring multiple specs to CR this year.
- Media Queries 4: There are several edits that need to be made to incorporate resolutions from previous telecons. Most of them can be done by Florian or TabAtkins; ChrisL will need to do a few that relate to Color. Florian will organize the effort to get these resolutions published. Florian will try and prepare the only unresolved topic for telecon discussion soon.
- Selectors 4: dbaron will add the language change he needs to write to github and try to write the changes soon.
- Box Alignment: There are multiple edits around grid resolutions that need to be edited in before republishing a WD. After that most remaining issues are around two value keywords and may be forked to a later level.
- Text 3: astearns will try and incorporate the pending edits and will reach out for help if he runs short on time.
- Transforms: astearns was actioned to remind people to incorporate the edits from the Lisbon F2F.
- There was a general agreement that more people could be involved in incorporating edits into specs. The “needs edits” flag will begin to be user regularly to indicate issues where this is a resolution reached but the spec needs it edited in. There was also a suggestion that a flag should be added to indicate what edits would be good for someone new so they can get their feet wet and more experienced editors can focus on harder edits.
- The end of year publication deadline is 19 Dec which means the last date for a CR resolution that could potentially be published this year would be 6 December.
Full Minutes
Minutes Telecon 2016-11-02
- Resolved: Change the text for
overflow:hidden not scrolling from SHOULD to MUST.
- Resolved: For the quoted Overflow spec text we are changing SHOULD to MUST and MAY to MUST.
- Resolved: No change on this issue (more detailed hyphenation policy).
- Resolved: No change to the spec because it already requires customary line breaking rules (in reference to this issue).
- Resolved: Use
place-items place-self place-content shorthands.
- The group will revisit the use of slashes once people have had more time to review and think through the implications.
Full Minutes
CSS Scroll Snap Candidate Rec Published
The CSS Working Group has published a Candidate Recommendation of CSS Scroll Snap. This module contains features to control panning and scrolling behavior with “snap positions”, to which the UA is biased to land after a scroll operation.
We expect some minor adjustments to be made to the module as we gather
implementation experience in the CR cycle, however the module should be
mostly stable now. Significant changes since the last Working Draft are listed in the Changes section and include renaming ‘scroll-snap-padding’ to ‘scroll-padding’ and expanding
its application to exclude the scroll padding area in other forms of scroll
position calculations, such as scrolling to a :target or using PageUp/Down
operations. (See https://www.w3.org/TR/css-scroll-snap-1/#scroll-padding for details.)
Please send feedback by filing an issue in GitHub (preferable) with the spec code ([css-scroll-snap]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Grid Candidate Rec Published
The CSS Working Group has published a Candidate Recommendation of CSS Grid. Grid 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 sub-component of the page.
This spec is the culmination of years of design. In 2005, Bert Bos published the first draft of Advanced Layout, containing the proto-forms of what would eventually become Grid and Flexbox (along with tabbed layout, which never became a thing). While this received occasional updates, the Grid part didn’t receive much implementor interest until 2011, when editors from Microsoft published the first draft of Grid Layout. This attracted the attention of fantasai and Tab, who’d always liked the very similar Template Layout proposal from Bert’s draft, and they gradually merged the two proposals into the Grid spec now being published. Yay for collaboration!
We expect some minor adjustments to be made to the module as we gather
implementation experience in the CR cycle, however the module should be
mostly stable now. Changes since the last Working Draft are listed in the Changes section.
Please send feedback by filing an issue in GitHub (preferable) 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.)
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: