CSS3 Values and Units Last Call for Comments
The CSS Working Group has published a Last Call Working Draft of CSS Values and Units Level 3. This module covers new units like rem (like em, but always relative to the root element’s font size) and vh (percent of viewport height) as well as the calc(), cycle(), and attr() functional notations.
Please review the draft and send us your comments! Best way to send feedback is to www-style@w3.org mailing list with [css3-values] and your topic in the subject line. (Alternatively you can email one of the editors and ask them to forward your comment.) The deadline for comments is 29 March 2012.
FPWD: CSS Transforms and CSS Fragmentation
The CSSWG published First Public Working Draft of two modules yesterday:
- CSS Transforms
- CSS transforms allow elements styled with CSS to be transformed in two-dimensional or three-dimensional space. This specification is the convergence of the CSS 2D Transforms, CSS 3D Transforms, and SVG transforms specifications. This spec is jointly-developed with the SVG Working Group: please send comments to public-fx@w3.org with
[css3-transforms] and your topic in the subject line.
- CSS Fragmentation Module Level 3
- This module describes the fragmentation model that partitions a flow into pages. It builds on the Page Media concepts from CSS2.1 and defines the CSS fragmentation model in a way that is generic to pages, columns, and regions and that future layout specs can hook into. It includes controls for pagination and defines with further precision the CSS breaking model. As usual, please send comments to www-style@w3.org with
[css3-break] and your topic in the subject line.
Minutes and Resolutions Telecon 2012-02-29
- Resolved: Publish Flexbox as WD.
- Resolved: Postpone the Transitions issues listed as postpone in dbaron’s message
- Resolved:
transition-* lists are aligned just like background-*, using transition-property as the master list (Bug 14604)
- Resolved: Reverse animations deferred from Transitions Level 1; but add example of how effect can be achieved now. (Bug 14611)
- Resolved: Remove mention of undefined
grid and zoom properties from Transitions spec (Bug 14618, Bug 14626)
- Resolved: vertical-align keywords are not animatable (Bug 14988)
- Resolved: No transition (no transition events fire) when
transition-delay and transition-duration are zero (Bug 15838)
- Resolved: Transform spec should make intersection behavior a MUST
- Discussed some concerns with migration to Mercurial for specs.
- CSS3 Images Disposition of Comments has been drafted, please review changes and proposed resolutions.
- Resolved: In Media Queries, add after “Relative units in media queries are based on the initial value” a clarification that units are never based on the results of declarations, instead of adding
rem example to clarify same point.
- Resolved: Move editors of Media Queries who are no longer active to “Former editors” list.
- Will shift Media Queries to PR next week, once implementation reports / testsuite are ready.
- Resolved: Drop comma between attribute name and type in attr().
- Resolved: Publish Last Call of CSS3 Values and Units.
Full minutes
Minutes and Resolutions Telecon 2012-02-22
- Discussed how much overlap to have in Hamburg with SVG
- Resolved: Publish CSS Variables as First Public Working Draft
- Resolved: Publish CSS Speech as Candidate Recommendation
- Resolved: Publish CSS Grid Layout as Working Draft
- Resolved: Single hg repository for all CSSWG specs (not repo-per-spec)
- Resolved: Add Aryeh as editor for CSS Transforms
- Resolved: Publish CSS Transforms as First Public Working Draft
- Discussed synchronization of
transform-origin and background-position positioning syntaxes
- Discussed intersection behavior of transforms
- Action All: review dbaron’s list of Transitions issues for next week
Full minutes
Everything You Ever Wanted to Know about the CSSWG -webkit- Discussions (AKA Minutes and Resolutions Paris F2F 2012 / Telecon 2012-02-15: Vendor Prefixes and -webkit-, Property Aliasing)
-webkit- Problem
It should be noted that this has been a topic of passionate discussion, and that it will take awhile not only for the CSSWG to agree on and execute a plan of action, but even for the Members to understand the nuances of each others’ positions. For example, Mozilla, Opera, and Microsoft are aligned on there being a problem that desperately needs addressing, potentially with desperate measures; but not on the exact details of what is problematic or how exactly to address which parts.
Part I: Monday
Discussed problem of WebKit monopoly on mobile and the consequent pressure for other engines to implement -webkit- properties. See also Tantek’s questions on designing a course of action.
Full minutes
Part II: Tuesday
Discussed specific actions WG can take to ameliorate the situation. Three approaches are available; chairs assert the WG can use all as needed:
- Dropping prefixes before CR (via legacy clause in the prefixing policy documented at
/TR/CSS)
- Splitting specs to move stable features faster (as is being done with CSS3 Text)
- Asking the chairs to assign high priority to those features (as done with CSS2.1 leading up to its REC)
Full minutes
Part III: Wednesday
- Brief discussion of whether to drop prefixes pre-CR for Transforms, Transitions, and/or Animations.
Full minutes
Part IV: Telecon
Discussed -webkit- prefixing situation and how to move forward on Transforms. Considerations included:
- whether to exceptionally unprefix transforms immediately or follow through with the process to CR.
- whether Transforms spec needed to be split into SVG/CSS or 2D/3D or some other way.
- whether to move to CR while deferring all issues raised by the merge
- whether to publish LCWD immediately, how long of an LC period would be
required, and how long it would take to finish resolving the issues
No consensus positions were found, and all parties left the telecon frustrated.
Time estimates for finishing work on Transforms however were agreed to be within 2-3 months if appropriately prioritized.
Full minutes. Anyone interested in this topic should also read the www-style follow-up by Sylvain Galineau (Microsoft).
Aliasing
Aliases are used both for vendor prefixed / unprefixed property pairs as well as for the word-wrap/overflow-wrap property and for the page-break-* properties (which are aliased to break-*). We discussed what, exactly, aliasing means:
- Resolved: When a browser supports multiple syntaxes of a single property, they’re treated as aliases in the cascade, such that last wins. In the OM, all variants show up, with equivalent values, regardless of which version was specified or which won.
- Resolved: The last resolution applies to WG-approved aliases. It MAY be used by browsers for handling prefixed versions as well.
- Resolved: When value aliases are supported, return the version that the author provided.
- Resolved: In media query feature strings, also return the version that the author provided.
Full minutes
Minutes and Resolutions Paris F2F 2012: On Layout — Flexbox, Linebox, Fragmentation, Writing Modes, Transforms
Flexbox
- Discussed switching
flex() back to a flex property.
- Discussed using margins for alignment in place of or in conjunction with
flex-item-align.
Full minutes
Line Layout
Steve Zilles presented a proposal for the scoping of the CSS3 Line Layout module (which needs significant rewriting since the previous publication). Scope would include
- line processing model
- defining line layout from 2.1 with more precision
- choosing baselines to use for alignment
- line grid proposal from Kyoto F2F (draft)
- possibly other stuff
Full minutes, Slides
Writing Modes
Discussion of UTR50 status, Microsoft’s proposal (to Unicode) for a better system for orientation data, and CSS text-orientation property.
Full minutes
Fragmentation
Rossen and fantasai produced a draft of a CSS3 module dedicated to breaking across pages/columns/regions/etc. (i.e. pagination).
- Resolved: Publish FPWD of Fragmentation.
Full minutes
Transforms
matrix() and matrix-3d() continue to take unitless numbers. Where they need units, they are implicitly px or px-1.
- Discussed status of issues, 2D/3D/CSS/SVG merge, and how fast it’s possible to make progress.
Full minutes
Minutes and Resolutions Paris F2F 2012: Errata for CSS3 Backgrounds and Borders, CSS2.1, and Media Queries
Backgrounds and Borders Level 3
- Resolved: Accept the proposed text for bidi splits and box-decoration-break (making it optionally applied to bidi splits)
- Resolved: Accept the proposed text for corner transitions (making it more undefined within certain limits).
- Resolved: Default color of box-shadows is value of
color property.
- Resolved: Accept proposed text defining a default object size for determining
border-image slice positions to be the border image area.
- Resolved: Accept proposed values of “Animatable” field for all CSS3 Backgrounds and Borders properties.
- Resolved: Republish Backgrounds and Borders CR as LCWD in order to errata it. Include an explanation of why we’re publishing a WD—that it’s still a CR-level draft, we just need to make errata. (The W3C process doesn’t allow for errata in CR.)
Full minutes
CSS2.1
- Discussed some gnarly margin-collapsing issues in CSS2.1
- Proposed that root element does not establish a BFC, but participates in one established by the ICB; resolution pending review. (Bug 15702)
- Discussed interaction of scrollbars with box model and whether spec prose requires fixing. (Bug 15880)
- Resolved: For percent heights inside auto heights, change “The value computes to
auto” to “The value is treated as auto for the purpose of calculating the used value” and fix the Computed Value line accordingly. (Bug 153992)
Full minutes: Part I, Part II
Media Queries Level 3
- Resolved:
dpi/dpcm in resolution media query uses CSS units.
- In section 4.11 (
resolution), append after the first paragraph “For printers, this corresponds to the screening resolution (the resolution for printing dots of arbitrary color).”
Full minutes
Minutes and Resolutions Paris F2F 2012: Regions and Exclusions
Regions
- There was a long argument on the design scope and usefulness of the spec, whether it’s a good idea to progress the spec without a having templates or pseudo-elements or some other mechanism that does not require the insertion and scripted manipulation of empty <div>s in order to benefit from it.
- Discussed drafting page templates spec for next F2F.
- Resolved: Bug 15159 for adding use cases to Regions spec is closed.
- Reviewed various other issues in the Regions draft.
Full minutes: Part I (Monday), Part II (Tuesday)
Exclusions
- Discussion of deriving shapes from images and other rendered content.
- Concluded to use first frame of animated images.
- Discussion of layout dependencies between exclusions and other layout models, and problems of mutual constraint resolution
Full minutes
Minutes and Resolutions Paris F2F 2012: On Syntax – Functional Notation, Values and Units, Nested Style Rules
Functional Notation
Full minutes
Values and Units
There are no known substantive open issues other than attr() syntax; plan to go to Last Call after that is resolved.
Full minutes
Nested Style Rules
Discussed various issues with nested style rules proposal including:
- Use of
& is troublesome for embedding in <style>.
- Object model is insufficient, and editability is problematic.
- Interleaving of declarations and sub-rules is problematic.
- Need to distinguish that this is a proposal to the WG from one vendor, not a WG-sanctioned draft.
- Invalidation rules could be improved.
- Prioritization with respect to other modules: there are already too many higher-priority items on the WG agenda for us to dedicate resources to this now.
Full minutes
Minutes and Resolutions Paris F2F 2012: Adminstrative and Publishing
Fullscreen
- Resolved: Propose to work on fullscreen as a joint item with Web Apps API.
Full minutes
Snapshot
- Resolved: The CSS snapshot will be published once a year, at the beginning of the year, and every time a new specification meets the criteria for being listed in the snapshot note.
Full minutes
Media Queries REC
Opera and Mozilla have builds that pass the test suite, giving us 2 implementations. Remaining work before REC:
- Wait for Opera to publicly release their passing build.
- Update Media Queries test suite on W3C site.
- Create implementation reports.
Full minutes
CSS3 Images
- Resolved: Mark everything in Images 3 as at-risk except gradients.
- Resolved: WAI-PF gets until 22nd of February to send LC comments, since they requested an extension.
Full minutes: Part I, Part II
Administrivia
- Resolved: San Diego meeting, August 13-15, hosted by HP
- Discussed ways of handling traffic on www-style. Chairs to play a greater role in shutting down useless threads, as identified by members. Tantek and fantasai to write etiquette guidelines / FAQ.
- Resolved: Move to Mercurial for specs, work on docs / setup
- Tantek proposed a new spec process with triggers for transitions. WG agrees the triggers are appropriate for triggering a discussion about process transitions, but shouldn’t be forcing anything to transition without discussion and consensus.
Full minutes: Part I, Part II
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: