2015 Snapshot and Prefix Policy Update
The CSS WG has finally published a new CSS Snapshot: the CSS 2015 snapshot. This includes the new experimental implementations policy aka “prefix policy”, which has been formalized from the 2012 San Diego discussions. (Finalized wording for this was the hold-up to publishing this update; fantasai kept finding less-scary things to do.)
The CSS Snapshot collects together the set of CSS specs that are known to be a stable implementation target, but may not yet have a full set of passing test results. It also includes guidelines on the responsible implementation of CSS, as agreed on by the implementer representatives in the CSSWG.
We hope this document helps people understand the current state of the CSS specs and to find what they’re looking for among the many documents published by the CSSWG. As always, please send feedback to the (archived) public mailing list www-style@w3.org
with the spec code ([css-2015]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Writing Modes Level 3 Updated CR
The CSS Working Group has published an updated Candidate Recommendation of CSS Writing Modes Level 3. CSS Writing Modes Level 3 defines CSS handling of various international writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left (e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and vertical (e.g. Asian scripts).
This update fixes a bunch of problems found in the previous Candidate Recommendation, resulting in a small number of major substantive changes. Important ones include:
- Dropping
sideways-left and sideways-right from text-orientation, assigning the sideways-right definition to sideways.
- Adding
sideways-lr and sideways-rl keywords to writing-modes.
- Dropping the
use-glyph-orientation value in favor of aliasing the SVG glyph-orientation properties to text-orientation.
All substantive changes since the previous Candidate Recommendation 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-writing-modes]) 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 2015-12-16
- These meetings will not be held on 23 and 30 December unless someone requests them on the internal mailing list.
- Resolved: Accept all the changes to Align:
justify-content: auto -> start / stretch (on grid / flex items)justify-content: stretch -> flex-start (on flex items)- ‘left’ and ‘right’ -> ‘start’ (when operating in the wrong axis)
- ‘flex-start’ and ‘flex-end’ -> ‘start’ and ‘end’ (on non-flex-items)
align/justify-items: auto -> start/stretch (depending on ‘display’)
- Resolved: Spec that the flex container must wrap around its content in all cases, both the min-content and max-content case.
- Resolved: Spec the heuristic as the behavior for multi-line flex in min-content.
- Resolved: Spec both behaviors, put a note explaining implementations are inconsistent, this can’t be relied on, the WG isn’t happy on this and plans to drop one, but can’t decide which.
- Resolved: Change the spec to say you don’t have to fit all the flex items on the page, you have to just fit one in regards to pagination.
- Resolved: Take Flexbox to CR
Full Minutes
Minutes Telecon 2015-12-09
- All working group members should note on the Doodle (available here– member only) if they’ll be available for the 23 and 30 December calls.
- TabAtkins said that he had filed bugs and is putting pressure on the teams handling gmail and calendar so that they no longer rely on the improper behavior for
border-image. Several implementors said they would be willing to change back to the spec behavior once the two Google properties are fixed as long as there isn’t a long tail of other sites relying on the bug. TabAtkins will report back to the group in January with any updates on a timeline for the fixes.
- Resolved: Accept the change for issue 5
- No one was prepared to talk about if the proposed approximation was the right solution to the problem with finding the intrinsic cross-sizes of flex items. Implementors should review the proposal (available here) before next weeks’ call and respond on the mailing list. Anyone who hasn’t given an opinion on the mailing list may be asked to give one on the call so that a decision can be made quickly.
- Resolved: Accept the change for issue 3 in Flexbox
- Most of the Align topics on the call were about changing items from ‘computed to’ to ‘behaves like.’ These items will all be deferred to next week to get more review.
- Resolved: Add the ‘normal’ keyword to
align/justify-self, align/justify-items and align/justify-content with bikeshed pending
- TabAtkins brought his proposal to address the possibility of font name being duplicated inside and outside a shadow DOM. The proposal would create a mapping where the external font is translated into a guaranteed unique name when passed into the shadow DOM. dbaron raised the possibility of instead using a function that gets the name from the scope, which was a cleaner solution. TabAtkins will write-up a new proposal using functions and send it to the mailing list for review.
Full Minutes
Minutes Telecon 2015-12-02
- There were some offers to speak at the developer meet up.
- Rossen will take over the Houdini talk since TabAtkins won’t be able to attend.
- astearns is willing to give the talk he’s giving at this week’s dotCSS conference.
- fantasai will do a talk on best practices.
- gregwhitworth offered to do a talk on a TBD topic.
- Bert was willing to speak if needed.
- Bert said that the local organization for the developer meetup was handled.
- Jihye introduced her proposed solution for handling the relationship between
polar-angle and animations in relation to the Round Display spec. The best path forward depended on if the computed value of polar-angle is an angle or stays as a keyword. Jihye will look for use cases of the property to determine which solution is the right one and present her use cases and conclusion on the mailing list.
- Most members of the group thought it would be possible to use polar positioning as a part of absolute positioning, but were unconvinced it was a good idea. bradk, who proposed the idea, was having technical troubles so the conversation will continue on the mailing list.
- There is a backlog in the test repo which needs to be worked through. The issue was raised on the telecon in hopes of having these specific pull requests addressed and to begin working on preventing this in the future.
- The idea of assigning who is responsible for testing was raised and, though it had been tried before, was still thought of as a good idea.
- A lack of QA people in the working group or any person in charge of testing overall were both noted as additional problems that should be a part of the conversation.
- The standard for accepting a test was briefly touched upon with several people expressing that it should be a lower standard than code.
- For now the conversation will continue on the mailing list and in a week or two we will check back to see if the backlog is starting to clear.
- Resolved: Replace
scroll-snap-destination with scroll-snap-padding
- Resolved: Replace
scroll-snap-coordinate with scroll-snap-align and scroll-snap-area
- Resolved: Add axis keywords to a property applied to the scroll container with added issues
- Both Will Change topics were editorial and discussion will stay on the mailing list.
Full Minutes
CSS Device Adaptation Draft Updated
The CSS Working Group has published an updated Working Draft of the CSS Device Adaptation Module Level 1. This specification provides a way for an author to specify, in CSS, the size, zoom factor, and orientation of the viewport that is used as the base for the initial containing block.
This update contains changes accumulated since 2011, so there’s quite a few of them.
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-device-adapt])
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 2015-11-18
- The issue regarding max-width and intrinsic sizes in a table scenario (details here) is on dbaron’s queue to address.
- Resolved: Change
system to system-ui in Fonts 4
- Florian re-introduced his view on
pre-wrap and pre-wrap-auto, but the right people to come to a conclusion weren’t available, so the conversation will continue on the mailing list.
- fantasai, TabAtkins, and dholbert were deemed the right people to solve the issue over intrinsic track sizes for min-content vs auto-minimums (details here). They’ll respond to the mailing list saying they’re working on the problem.
- There was a proposal from glazou to take advantage user-select to create controls as to if generated content should be copy/paste-able.
- This solution seemed like it would only work for browsers implementing multi-range (currently only Gecko)
- Florian will write a note suggesting to browsers that if they do implement multi-range, they should also use user-select to create these controls and glazou will review it.
- It was reaffirmed that not all generated content needs to be or should be copy/paste-able and therefore the solution needs to be a switch and likely should default to turned off for backwards compat.
Full Minutes
Minutes Telecon 2015-11-11
- Resolved: Publish new WD for Device Adaptation.
- MaRakow, TabAtkins, and fantasai got a chance to speak and come to a consensus on how to fold the change in approach to snap points into the existing WD. This change-over will occur over the next several weeks.
- Once the new version is ready, the group will publish a last version of the old approach right before publishing the new approach, both as WDs. This allows a good record of how the spec progressed without sending the wrong signal about the direction of the spec to implementors.
- There was support for the proposal of 2D rotation transform function for polar coordinates, though it was thought they should be named polar-angle and reverse-polar-angle or polar-reverse-angle to explicitly link them with the polar properties. An additional question was raised about how it would interact with animation, but it was decided that that interaction was dependent on if it’s a computed value or a specified value.
- Resolved: Accept the proposal for a 2D rotation transform function for polar coordinates and make it clear if it’s a computed value or a specified value and make a note on the implication of that decision on animations.
- Resolved: Accept the polar-origin changes.
- The polar-origin proposal lead to a conversation about adding a center value to fixed and absolute positioning. The conversation will continue on the mailing list. However, if this change ends up happening, it may negate the need for polar-origin.
- There wasn’t telecon time for a full conversation on the mailing list conversations around page floats, but it was suggested that the interested parties get on a separate call to work through the mailing list topics. johanneswilm and Florian will work on organizing a call.
- Resolved: Line-grid will restart in the case of orthogonal flows between parent and child.
- Resolved: Add JIS-B4 and JIS-B5 to paged media.
- Florian will summarize other page sizes that could be added to the spec in an e-mail.
Full Minutes
Minutes Telecon 2015-10-21
- Anyone with items to discuss at TPAC is asked to please put them on the agenda ASAP.
- The Japanese Industry meet-up is still short on details, but Florian is speaking with them tomorrow, so hopefully the details are forthcoming.
- Jihye brought her proposal for a polar orientation property to the working group for their feedback. The group felt that the effects of the property could be achieved by the rotate property either as it stands or with additional keywords aimed at handling polar cases easier.
- Florian also expressed a concern that the proposed behaviors in polar orientation may not be enough to solve common use cases and requested an issue be added that there may need to be more keywords.
- Resolved: Publish CR for Writing Modes.
- Everyone agreed that the spec text for
word-break: break-all needed re-working, though there wasn’t a clear decision on the right direction. Koji and fantasai will come up with a proposed change to the spec referencing UAX14 and see what the group thinks of it.
- The working group is in favor of any changes to the default TR stylesheet that brings it closer to the stylesheet that the CSS working group is already using.
- The Will Change and Variables specs have received resolutions for publication, but have not actually been published.
- Bert will look into where these specs are in the pipeline.
- There are also specs with last publication date of more than 6 months ago. This issue will be discussed at TPAC.
- Resolved: Publish Cascade 4 as CR
Full Minutes
Minutes Telecon 2015-10-07
- Everyone was reminded to add items to the wiki for TPAC conversation.
- The Houdini task force will meet on the Thursday of TPAC. They may also hold a breakout session on the plenary day depending on if there are proposals for specific topics and/or meet on Friday if they need more time.
- Resolved: Adopt Section 3 of the Snapshot.
- Resolved: Publish Snapshot.
- Florian and fantasai agreed that the spec should say something along the lines of the UA must provide a smart behavior and should match platform with ‘be smart’ defined as ‘provide a good experience’. They will work on solidifying the wording.
- Resolved: In
pre-wrap, disallow wrapping before the first space.
- The right people weren’t on the call for a resolution regarding the behavior of
scrollLeft in RTL or vertical-rl mode, but webkit plans to change to be more consistent with the proposal.
- Using
start and end for positioning needs a consistent decision between all 2d positioning, not just for floats. It was added to the TPAC agenda.
- There was a strong feeling from Rossen that there wasn’t a need to make Grid and Flexbox consistent in their
auto value for alignment. The spec will be left as-is for now and fantasai will look for more feedback, especially from authors.
- Resolved: Issue #19 for Framentation is out of scope.
- Resolved: Take Roc’s suggested wording about keeping inline blocks non-fragmented (Issue #21 for Framentation)
- Resolved: Each fragmentainer must contain at least some content or fragment of content.
- Issue #24 for Framentation, adding
force to the page, column, and region keywords, still needs to be discussed either on a call or at TPAC.
Full Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: