CSS WG Blog front page
Minutes Telecon 2015-09-09
- Resolved: Accept the change for behavior of cloned margins at breaks in Fragmentation.
- Resolved: Publish Fragmentation as CR.
- fantasai will clarify the meaning of prefixing in sections 3.3.2 and 3.3.3 of the Snapshot 2015. Microsoft and Apple will send it around to interested parties asking for input for next week’s call.
- Resolved: Accept the new wording to put a conformance requirement on authoring tools that whenever they reorder something visually, it’s reflected in the DOM, (full text available here) pending bcampbell’s feedback.
- Resolved: No change for baselines on flex and grid containers.
- Resolved: Revert the decision to change ‘0’ -> ‘0%’ in Flexbox and note in the spec there’s a chance there might be a webcompat issue.
- Resolved: Simplify spec to restrict
auto-fit to only take single track sizes as an argument. Leave issue open asking for use cases, and switch back if needed. Turn the issue into a note at CR saying a future level might expand.
- Resolved: Republish Grid with the changes discussed during the telecon.
- Everyone was tasked with reviewing Grid so that the authors can stay on target to publish CR during TPAC.
- glazou urged progress on three very visible specs, Transforms, Transitions, and Animations, and will also be reviewing the rest of the specs before TPAC to make sure that nothing has stalled progress.
- Though official confirmation is pending, the Japanese industry meeting will likely occur on the Sunday before TPAC.
CSS Cascade 4: Last Call for Comments
The CSS Working Group has published an updated Working Draft 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:
Since we have no open or anticipated issues, we plan to transition this module to Candidate Recommendation in about four weeks. We do encourage people to review the draft, particularly the changes since Level 3, and send us comments. Changes since the last Working Draft are listed in the Changes section.
As always, please send feedback to the (archived) public mailing list firstname.lastname@example.org with the spec code (
[css-cascade-4]) 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-08-12
- It was clarified that the ‘system’ keyword will be in Fonts 4.
- jdaggett will work with TabAtkins and fantasai to put Fonts 3 into bikeshed working through the issues that jdaggett has had in the past.
- The proposal from Myles regarding introducing small-caps into font-synthesis was discussed.
- There was concern that the use case was just theoretical, not actual, though dauwhe said that he has to make sure there is no use of synthetic small-caps in his work.
- Several members argued that they believed there needed to be a fallback for when small-caps isn’t available.
- Resolved: support small-caps in font-synthesis in Fonts 4
- Specifying how keyframes interact topic will wait until the F2F in Paris to make sure that Mozilla is okay with the change.
- Resolved: unprefix min/max-content
- gregwhitworth will work on building out a test suite for CSS Sizing
- Discussion of Ruby issues will also wait until the F2F.
- Fantasai’s proposal regarding max-content contribution not being defined for flex items needs review, especially from TabAtkins and dholbert, so it will also wait until the F2F.
CSS Grid Layout Update, Request for Comments
The CSS Working Group has published an updated Working Draft of CSS Grid Layout Level 1. This module 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 components.
We hope to close the remaining issues over the next month and prepare to issue a Candidate Recommendation this fall, so please review the draft and the issues and send feedback! We want to make everyone happy, but that won’t happen if you complain after we’re done and everyone’s already shipped their implementations and you only bother to tell us you don’t like something two years later, yeah? So review now, and complain sooner rather than later.
Changes since the last Working Draft are listed in the Changes section, and since we forgot to announce the previous few publications on this blog, you might also want to check March 2015 and May 2014 if you’re interested specifically in changes. The most significant changes over the last year include
We welcome all feedback, particularly from Web authors. If you need a layout to align in two dimensions, this is the module for it, so make sure it handles the things you need! Please help us make this module more correct, more useful, more usable, and more readable!
As always, please send feedback to the (archived) public mailing list email@example.com 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.) Known issues are listed in in this issue-tracking list.
Minutes Telecon 2015-08-05
- bkardell informed the group that
:has() has received a lot of support on Microsoft’s uservoice.
- Resolved: In case of one single supports query the innermost parentheses are optional in functional notation
- This resolution applies to both JS and
- Resolved: Leave the spec as-is for
contain: paint and
- Resolved: Clarify contain to make sure it specifies the order of operations
- Resolved: Accept the new ‘system’ value and its definition with a note in the spec about fingerprinting issue.
- Resolved: Add LCH to the Colors 4 spec
- Everyone on the call was in support of the proposal to create
writing-mode, but all the interested parties weren’t on the call, so a decision will occur on the mailing list.
- Resolved: Revert the Media Queries spec on the whitespace requirement
- Everyone received an action to review TabAtkins’ proposed algorithm for handling how animations interact with each other when one has an animation timing function and others don’t
Minutes Telecon 2015-07-29
- Resolved: Publish updated WD of Grid Layout
- There was still no consensus on what to do with the name ‘any’ in CSS Break, though it was agreed to be troublesome. Possible solutions were:
- Accept the name
- Rename it
- Push it to level 4
- Change ‘always’ to ‘all’ so that ‘any’ would make more sense
- There was no consensus so discussion will continue on the mailing list.
- As the percent resolution for abspos vs inflow grid items issue is dependent on a F2F topic, a final decision will hold off until the Paris meeting.
- There were three proposed solutions to address
- A) “overflow: clip” is a paint only operation, it does not (on its own) create a BFC, and if “contain” is not “paint”, you can have “overflow-x:clip” in one dimension and “overflow-y:visible” (and vice versa). Amend the definition of “resize” and “text-overflow” (and anything else that depends on “overflow”) to deal with the new possibility of being visible in one dimension only.
- B) Rename to “overflow: hidden no-scroll”. It creates a BFC. If you specify it in one dimension only and leave the other visible, the visible one computes to auto.
- C) Don’t introduce a new value to overflow, make “contain:paint” cause “overflow:visible” to compute to “overflow:hidden”, and implement heuristics to detect when browsers should avoid allocating the resources needed to do the scrolling.
- The group first discussed the merits of A before deciding to rule it out completely. C seemed like the ideal case, but browsers weren’t capable of it yet, so the group decided on B. There was a mini bikeshedding session after the telecon on IRC where ‘clip’ and ‘none’ seemed to be the most favored, but the decision is still up in the air.
- Resolved: pick option B behavior, defer naming to editors, everyone complains if they pick something bad
Minutes Telecon 2015-07-22
- Resolved: Publish new WD for CSS Cascade Level 4
- The group discussed a the e-mail from fantasai regarding what portions of Selectors 4 should be deferred or discussed as Selectors 4 is prepared to move to CR. The entire group received an action to read and respond to the entire e-mail (available here).
- Most of the conversation centered around
- There is some disagreement about how
:has() should work and there are no implementations to date and therefore it was suggested that
:has() shouldn’t be in CR. It was agreed to put it at-risk for now with a note indicating what the disagreement is.
- There was a feeling that
:has() has been discussed so many times and that developers want
:has() so much that just deferring it to the next level would reflect poorly on the group. It was expressed that if
:has() is dropped or deferred the group needed to publicly post an explanation in order to help the community that is so excited to understand the process of the decision. In the meantime, several people will post and talk about :
:has()‘s at-risk status in order to encourage the community to push for implementation if they really care about having it.
- The draft still needs an updated WD publication, but fantasai expressed that she needed more time to do a through review of the spec. There is a hope that the publication will be ready for voting next week.
- There was a desire to have more time to read the small details of the proposed text for CSS Snapshot 2015 before any resolutions. Some browser vendors expressed concern about the language aimed at limiting prefixing was imprecise and perhaps too harsh, though no one was disagreeing about trying to limit prefixing.
- Resolved: add Florian as an editor to the CSS Snapshot 2015
- Resolved: add TabAtkins as an editor to the CSS Snapshot 2015
- fantasai’s proposal to drop cloned margins at any break seemed to be right to everyone, but the topic will wait a week for people to review the exact wording and look at examples.
user-select: none is a useful feature and we won’t drop it.
Minutes Telecon 2015-07-15
- The question regarding CSSOM and Grid will be deferred for a week to let people read up on the issue.
- Resolved: We change to ‘element’ to ‘contain’ for
user-select for now and make the final decision next week.
- Everyone pretty much agreed that the cursor property shouldn’t be altered, so the word ‘default’ needed to be changed in Cascade Level 4. Some of the top names that were discussed were ‘rollback’, ‘default-value’, and ‘rewind’. Originally the group resolved on changing it to ‘rollback’ and having a new note saying other suggestions were welcome. However, there was a late suggestion in IRC and the group changed their mind.
- Resolved: Rename ‘default’ to ‘revert’
- Several developers expressed that they had severe concerns about animating caret. Florian will gather examples from the web of where caret is being animated and create a proposal that covers those use cases.
- There was continued high interest in figuring out how to use the existing CSS properties for Rounded Displays. Hyojin will send a follow-up e-mail to the mailing list with visual examples of what he’s looking for
border-boundary to do in respect to rounded displays.
Minutes Telecon 2015-07-08
- Everyone was okay with having some overlap time with the SVG WG during the Paris F2F instead of during TPAC.
- Resolved: keep images and an images/ folder and source files in a source/ folder for each spec.
- Clarification on percent margin/padding was deemed editorial and will be addressed by the editors.
- Resolved: add
- One of the blockers for the conversation about the relationship between
overflow: clip and BFCs was the use of the word ‘clip’ when it really was a property to just do
overflow: hidden, but not allow scrolling. If the property is re-named (hidden-no-scroll was the name used in the call) a main objection will be removed. A larger issue as to if this is solving an important problem was also raised. One side was that this is along the same lines as
will-change that allows authors to indicate intentions in order to speed up the browser. However, the same argument that
will-change was fixing an implementor issue can also be applied to
overflow: clip. Florian will write an e-mail summary of the conversation and the options moving forward to continue the conversation forward with input from those that weren’t on the telecon.
- During the conversation about variants of pre-wrap and longhands of the white-space property the third option in Florian’s list of suggestions (available here) was discovered not to be a potential solution. It was instead replaced by eliminating the white-space longhands that are causing the problem. Discussion will continue on the list.
- The conversation on bikeshedding
user-select: element will wait a week so that people can review the history of this property.
CSS Basic User Interface Module Level 3 Candidate Recommendation Published
The CSS WG has published a second Candidate Recommendation of CSS Basic User Interface Module Level 3. This specification describes user interface related properties and values that are proposed for CSS level 3, incorporating such features from CSS level 2 revision 1, and extending them with both new values and new properties.
Call for Implementation
This notice serves as a call for implementations of all CSS-UI-3
features, new properties, values, and fixes/details of existing
features. Implementor feedback is strongly encouraged.
Thorough review is particularly encouraged of the following features
new in level 3:
Significant changes since the previous 2012 LCWD are listed in the Changes section.
This CR has an informative “Considerations for Security and Privacy” section with answers to the “Self-Review Questionnaire: Security and Privacy” document being developed by the W3C TAG.
Please send feedback to the (archived) public mailing list
with the spec code (
and your comment topic in the subject line.
(Alternatively, you can email one of the editors and ask them to forward your comment.)
This post originally appeared on http://tantek.com/2015/189/b1/css-basic-user-interface-level-3
Browse by date:
Browse by category: