CSS WG Blog front page
Minutes Telecon 2013-10-23
- Resolved: Accept work on Scroll Snap Points as an Editor’s Draft
- Plinss asked everyone to add discussion items for TPAC to the agenda wiki. Concern was again expressed that there was no answer on if there was a room for the group to meet in on Sunday. Plh said he’d look into it. Later in the meeting, Plh confirmed that there was a room set aside for the Sunday meeting.
- Everyone was reminded that next week Europe will end daylight savings time, but the US and therefore the telecon won’t switch until the week after.
- Plinss requested that everyone remind their reps to vote positive on CSS Style Attributes.
- Stearns requested responses on the mailing list to his comments about Named Flows and Box Generation.
- The feedback from the web platform team about
outline-style: auto will go through the normal spec comment process.
- Michou brought up his question on how fragments are handled in Fullscreen. The group felt that fragments should be ignored in Fullscreen, but that this should be addressed in Fullscreen, not in fragments. Therefore, Michou will provide his feedback on that mailing list.
- Discussion on
!important were deferred until zcorpan was available, perhaps at TPAC.
device-pixel-ratio should interact with zooming was discussed which included conversation about the different types of zoom. Proposals included having
device-pixel-ratio only respond to one type of zoom, creating a different property for different types of zoom, and differentiating between zoom that changes the width and zoom that doesn’t. No resolution was reached and discussion will continue on the mailing list and, if needed, at TPAC.
- Resolved: Publish another working draft of Writing Modes
Minutes Telecon 2013-10-16
- Howcome explained why he wanted the move Generated Content for Paged Media (GCPM) and Page Floats to the WHATWG. The implications to the working group of this move were discussed. This includes how WHATWG documents have been used with other W3C projects and what future steps will be. No conclusion was reached as Howcome had to leave the telecon, but the conversation was productive.
- Stearns and Fantasai will continue their conversation about Shapes on the mailing list to reach an agreement.
- Stearns requested feedback on his comments about Regions and Overflow.
- Fantasai requested that the group move Writing Modes to last call in order to get a comment period completed before TPAC. She views the one outstanding issue as minor and thinks it can be addressed in last call between herself, Koji, and Jdaggett. Glazou will e-mail Jdaggett to see if he is okay with this proposal.
- ChrisL requested more comments to be posted on the proposed recommendation on CSS Style Attributes.
CSS3 Text Last Call for Comments
The W3C CSS Working Group has published a Last Call Working Draft of the CSS Text Module Level 3. This module covers various aspects of text layout including white space processing, text transformations, line breaking, justification, and indentation, including additions to level 2 to address internationalization concerns, allowing better typography in non-Western (and Western) scripts. Significant changes since the previous are listed in the changes section
The deadline for comments is Thursday 7 November 2013. If you need more time, please request an extension before the deadline so that we know to wait for your comments. We plan to process the bulk of the LC comments that weekend and during TPAC the week after. It’s okay if you need more time, we just need to know about it.
We would especially appreciate a detailed review from the following typographic communities where we are missing expertise, particularly on the topics of line-breaking and justification:
- Southeast Asian
As always, please send feedback to the (archived) public mailing list email@example.com with the spec code (
[css-text-3]) 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 2013-10-09
- SimonSapin asked for information on how to add an errata to the CSS Style Attributes. Bert will help him out.
- Resolved: CSS Masking to Last Call with a 6 week period.
- Resolved: Split DOMMatrix, DOMPoint and DOMPointLiteral to own editor’s draft.
- Rossen sent a clarification of his thoughts on Writing Modes section 5.1.1 to the mailing lists, the implications of which were discussed.
- Fantasai summarized the issues with glyph replacement when the item is rotated.
- The group then began discussing the various solutions possible; Fantasai will send an e-mail to the group summarizing the three options available.
- Stearns stated that most of the feedback received for Shapes syntax has been reflected in the current editor’s draft.
- The remaining issue is if shapes should model off of SVG, CSS position, or both.
- Further discussion will occur on the mailing list.
CSS Cascade Level 3 Candidate Recommendation
The CSSWG recently published CSS Cascading and Inheritance Level 3 as a Candidate Recommendation. W3C encourages implementations of this module, and welcomes feedback resulting from such implementation. Requests for new features will be assigned to Level 4.
CSS Cascading and Inheritance Level 3 describes how to collate style rules and, by way of cascading an inheritance, assign values to all properties on all elements in the document. New features since the previous level (CSS2.1) include:
The spec also collapses all inputs to the cascade into a single list, making it easier to understand how different levels appended to the CSS2.1 definitions fit together.
Significant changes since the Last Call Working Draft are listed changes section.
As always, please send feedback to the (archived) public mailing list firstname.lastname@example.org 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 2013-10-02
- Resolved: Publish a new working draft of Generated Content for Paged Media (GCPM).
- Page Floats will be discussed later when Hakon is on the call.
- Resolved: Krit and Rik will be co-editors for DOMMatrix, DOMPoint and DOMPointLiteral
- Decision to publish a new editor’s draft for DOMMatrix, DOMPoint and DOMPointLiteral taken to e-mail on W3C-CSS-WG mailing-list after misunderstanding and invalid decision during call given the request. Correction made by co-chair Daniel (glazou) after end of the call.
- All but one issue has been addressed for Shapes. Astearns requested another week to work through the syntax issues on the remaining issue.
- The different ways that various specs point to elements were discussed. Some testing will be run to see what method current implementations are using in order to determine how to proceed.
- The group expressed an interest to have a few hours meeting with the SVG WG during the Wednesday of the January F2F in Seattle.
- Glazou will talk to Bert further about finding out if the WG will meet on the Sunday of the November F2F.
Minutes Paris F2F Sept. 2013 Part III: Masking, Display Tree or DOM, Flexbox, Color Module, Charter, Ruby, Text, Writing Modes, Animations
CSS Masking – Review Request
- Resolved: The WG will review Masking LC transition on the 10/9 telcon
Any interest in working out selection/editing based on display tree rather than DOM?
- Though some interest was expressed, it was deemed currently not enough to proceed to an ED
- Resolved: Use 2-pass algorithm to resolve % height children of flex stretched items pending dholbert’s feedback.
- Resolved: Proposed issue-1 edits are approved.
- Resolved: Add ChrisL as co-editor on CSS4 color
- Resolved: Pull in SVG2 color section into CSS4 color
rgba() will accent
number rather than
- Resolved: Allow
angle in place of
number for hues
- Resolved: Accept
- Resolved: Accept rgba hex colors
- Resolved: No change to number of arguments to rgb/hsl
- Resolved: Add
color-correction property to CSS4 color draft, with issue about the problem it’s trying to solve and consideration that it might not be the right solution.
- There was discussion about how to handle timelines for specs as a part of the rechartering process.
- The group also discussed possible alterations and alternatives to the current charter model that may better fit the process of the WG.
- It was decided that the chairs, plinss and glazou, would draw up a list of priorities from existing WG documentation and submit it to the WG for review and approval before inclusion in the charter documentation.
- The new proposal for CSS Ruby was discussed section by section. The WG had several questions and concerns about most sections, but decided to move to Working Draft after fantasai added some text clarifying the intention of the
- Resolved: Publish fantasai’s CSS Ruby draft as a Working Draft.
letter-spacing: length doesn’t restrict justification.
text-justify:inter-word; disables inter-letter justification.
letter-spacing:normal; computes to 0.
- Resolved: Spec the dependence of
text-align:justify and mark issue for feedback on shorthanding vs. not.
- Resolved: Drop minimum/optimum/maximum values for word-spacing.
- Resolved: Keep
text-align: start end in, add an issue about naming, and mark it at risk.
- Resolved: Take css3-text to last call pending resolving issues from jdaggett.
- Koji found a difficulty from the decisions made regarding
tcy and writing modes yesterday.
- Resolved: Drop digits 1
- Resolved: css3-writing-modes to Last Call when edits agreed in this meeting are completed.
- dbaron brought the group up to speed on the changes he had made to the spec.
- The order in which events will fire and boundary points were of particular concern, but it was decided that an e-mail conversation and testing were the best way to answer the outstanding questions.
Minutes Paris F2F Sept. 2013 Part II: Font Load Events, TPAC & F2F Schedule, Masking, Naming of DOMPoint Quad and Matrix, Sticky Position, Text-Combing Naming, GCPM, Writing Modes, Compositing Spec
Font Load Events
- Discussed possible new spec for font load events, including improvements on the explanatory text and security concerns about
FontFace interface issues were also discussed. TabAtkins requested that others review the spec to allow for implementation to occur.
TPAC and F2F Scheduling
- Still looking for a space for a Sunday meeting at Shenzhen in November.
- Tentative resolution for Jan 27-31, joint meeting with SVG, in Seattle, hosted by Adobe.
- Investigating Asian locations for week of May 12-16.
- Sophia some time in September.
- Resolved: The
mask-image property only takes one layer.
- Resolved: Combine CSS Images and CSS Mask references in the SVG mask references.
- Resolved: Default value for
- Resolved: Add keyword
- Resolved: Default for
- Resolved: Default for
Naming of DOMPoint, Quad, and Matrix
- Resolved: Provisionally go for DOM prefix.
- The group agreed that
Sticky would add good functionality.
- Rossen will add text about
Sticky to the Position module.
- Resolved: add Rossen as editor to Position module.
- Options for
Text-Combine name was discussed, but no solution was decided.
- Ideas floated include
- Resolved: Publish sections 1-5, 7, and 13 of GCPM ED as a new working draft.
- Resolved: Move section 6 to CSS3 Page; section 8 to CSS Color; section 9 to CSS3 Page; sections 10, 11, 14 to Overflow; section 12 to Page Floats (new spec); section 14 to Overflow (for now, Pseudo-Elements when we write it); section 15 removed; sections 16 and 17 to Page Floats.
Specs Referenced: GCPM, Page Floats, CSS3 Page, CSS Color, and Overflow
CSS Writing Modes
- Various options were discussed to address the inheritance of
text-combine-horizontal. The group came to three options, but decided to continue the conversation later to decide between those choices.
- Koji will update the spec to UTR50
- Rossen check if it’s ok to drop support for
text-combine-horizontal: digits 1
Issue 2 in Compositing Spec
- Resolved: Close issue #2
- Resolved: Everyone review Compositing/Blending, we’ll take up the question of Last Call publication at next telcon.
Minutes Paris F2F Sep. 2013 Part I- Grid Layout, Style Attributes, Spec Preprocessor, CSSOM, Image Values, Multi Column Layout, Shapes & Regions, Transforms
- Resolved: Formally accept renaming
- Resolved: Grid child static position is resolved as if it’s the sole child. The definition will also be copied over to Flexbox.
- Resolved: Add more examples to the absolute position grid items section.
- Resolved: Named areas create implicitly named lines.
- Resolved: Make named areas just desugar into named lines.
- Resolved: Leave subgrids in level 1, mark it and its component parts individually as at-risk.
getComputedStyle returns used values for
- Resolved: Don’t change
- Resolved: Take Style Attribute to Proposed Recommendation, with explanation of
xml:base interaction test failure as an
Tab presented his new spec preprocessor, Bikeshed.
setProperty‘s handling of importance logically behaves same as appending a declaration (like IE/WebKit).
- Resolved: Add a
setPropertyPriority application programming interfaces.
CSS Image Values
- Resolved: When transitioning from plain image A to
foo(A), infer the
foo() on the other side (using no-op arguments).
- Resolved: Mark as open issue whether interpolating complex images with the same source (e.g.
bar(A)) uses recursive interpolation (building a stack of compatible functions, e.g.
foo(bar(A))) or just uses
- Resolved: Accept proposal to shift misordered gradient stop fixup rules to after missing position interpolation and transition interpolation in order to make transitions layout-independent.
- Resolved: No magic length interpolation for angle transitions in
- Resolved: Cannot interpolate to/from gradients with keyword direction unless using the same keyword.
- Resolved: Discussed layering order of column rules.
- Resolved: Columns do not clip anything. (As if
::column just had
overflow:visible by default).
- Resolved: Remove the restriction about overflow columns only being in continuous media with the statement that
column-fill has no effect on overflow columns.
- Resolved: Have two keywords for balancing –
balance and either
balance-all, depending on what implementations (including Prince and Antenna House) do by default.
- Resolved: To balance columns, you just make the row as short as possible (honoring breaking controls, sizes, etc.), then flow normally into that height. No explicit “balancing” occurs (but it’s a common effect).
- Resolved: Håkon to create a public, editable, full list of issues with source, response and resolution. The format is up to him.
Shapes and Regions
- Mihai Balan to become test owner for Regions.
- Resolved: Conditional agreement on taking Shapes to Last Call. The final yay/nay will be at the telcon in two weeks.
Spec Discussed: Regions Shapes
Discussed possible syntaxes additions for making transform lists easier to interpolate. One idea discussed was using commas to group transforms. This had a number of disadvantages, one of which is incompatibility with SVG syntax. Another idea was introducing a null transform, which would be compatible with all transforms and to use as a placeholder in a list. No conclusions and no changes to this level.
There was also a brief diversion into the idea of editing only one segment of a list-valued property.
Minutes Telcon 2013-09-25
- Resolved: RESOLVED: Publish CSS Compositing and Blending Level 1 as Last Call.
- Everyone will review GPCM and Page Floats for next week’s telecon.
- Resolved: TabAtkins to put
overflow: clip to new Editor’s Draft.
- Resolved: Use
doubles instead of
float for matrix items.
- Remaining issues for
DOMPointLiteral were deferred until next week.
- The group discussed the need for and use of
device-cmyk(). No conclusion was reached by the end of time, so the discussion will be continued on the mailing list.
Browse by date:
Browse by category: