CSS WG Blog front page
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 firstname.lastname@example.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
- 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.
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 email@example.com 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.
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: Change the initial value of
- 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.
align-content to stretch
There’s still no final location for the May F2F.
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 firstname.lastname@example.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:
text-orientation, assigning the
sideways-right definition to
sideways-rl keywords to
- Dropping the
use-glyph-orientation value in favor of aliasing the SVG
glyph-orientation properties to
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 email@example.com 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
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.
Browse by date:
Browse by category: