CSS WG Blog front page

This is a page from the Cascading Style Sheets Working Group Blog. Some other places to find information are the “current work” page, the www-style mailing list, the Future of CSS syndicator, and the issue list on Github.

Do you want to know how the CSS WG works? Fantasai has written about:csswg, An Inside View of the CSS Working Group at W3C.

Minutes Telecon 2018-07-18

• Resolved: Add Chris Lilley as editor to Fonts 4
• Resolved: Keep it that blockification and establishing formatting context are independent (Issue #2673)
• As a part of the discussion for issue #2673 it was raised that part of the reason blockification and establishing a formatting context were requested to be linked is the earlier resolution to make inline flow-root and inline block the same. Over the next week people will re-look at that decision (Issue #1246) and re-open it if necessary.
• Unless there is a new issue opened, next week there will be a CR publication request for CSS Display.
• Resolved: Have PR #2924 as the start of a set of constraints with Gecko algorithm as an example in a note.
• Resolved: Keep current definition such that we could all lines in overflow:clip descendant (Issue #2421)
• Resolved: Handle percent text-indent in intrinsic size box same as percent in padding and margin (Issue #1597)
• Resolved: Defer this issue (#2390: Implement or unship word-break:break-word) for now [to Level 4]

Full Meeting Minutes

Updated CR of CSS Text Decoration Level 3

The CSS Working Group has published an updated Working Draft of CSS Text Decoration 3. This module contains the features of CSS relating to text decoration, such as underlines, text shadows, and emphasis marks.

This update closes out a variety of issues filed since the previous publication in 2013. See the Disposition of Comments. Significant changes since the last Candidate Recommendation are listed in the Changes section.

Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-text-decor-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 2018-06-27

• Resolved: Add environment-blending to Media Queries 5 (Issue #2723 | PR #2719)
• There was a desire to make the change in Issue #927 (Smarter interpolation of truncated transform lists) either in level 1 or not at all so that it maintains interoperability. No implementor on the call showed interest in this change, but two key commenters from the github issue (birtles and TabAtkins) were not on the telecon so the final decision will be deferred to the F2F.
• After discussion the group came up with five options to address the request in Issue #2757 (Consider disallowing NULL code points in stylesheets)
  1. drop entire stylesheet
  2. drop stylesheet after NULL
  3. drop encompassing selector around NULL
  4. drop NULLs during pre-parse
  5. no change
  • Some members of the group were unconvinced of the use case behind the issue and wanted to have someone with security expertise validate the vulnerability. The group will review again at the F2F and perhaps request review from TAG.
• Resolved: compute to none [instead of behaves as none] (Issue #2755: Use “computes to” instead of “behaves as” for display: contents on unusual elements)
• Resolved: Change to “behave as” instead of “compute” (Issue #2708: Incorrect use of the word “compute” in definition of intrinsic keyword values)
• Resolved: Accept the proposal in Issue #2465 (instead of having break-spaces be a || alternative in overflow-wrap, it will be a | alternative in white-space.)

Full Meeting Minutes

CSS Basic User Interface Module Level 3 reaches Recommendation

The CSS WG has published the CSS Basic User Interface Module Level 3 as a Recommendation.

This specification describes user interface related properties and values to style HTML and XML. It includes and extends user interface related features from the properties and values of CSS level 2 revision 1. It uses various properties and values to style basic user interface elements in a document: box-sizing, outline (and related longhand properties), resize, text-overflow, cursor, and caret-color.

There were a few editorial changes since publication as a Proposed Recommendation, listed in the Changes section. An Implementation Report is available.

Errata will be maintained as necessary. Further refinements or extensions on the topics covered by this specification continue in CSS Basic User Interface Module Level 4, except for the box-sizing property, which will be maintained in the CSS Intrinsic & Extrinsic Sizing Module Level 3.

Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-ui-3], [css-ui-4], or [css-sizing-3] as appropriate) 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 2018-06-20

• Resolved: Change to ‘should’ in L3 [for synthesizing super/sub-scripts] and push for it in L4. (Issue #2796)
• Resolved: Request transition to proposed rec for Fonts L3.
• The group discussed the proposal to have the filter apply to the viewport when applied to the root element. (PR | FXTF issue)
  • There were concerns that this would yield unexpected behavior for authors since they would expect the filter to be applied to the entire page, not just the viewport, and might see a shimmer when scrolling.
  • Applying to the entire page was thought to be extremely complex, if not impossible, implementation-wise for some filters like blur.
  • There was no agreement on how best to balance author expectations and implementation needs, so use cases will be gathered on github to further the conversation.
  • The original resolution that lead to this proposal, “non-none values of filter induce a containing block for all positioned descendants”, may also need to be revisited since it’s what necessitated this proposal.
• Resolved: Use Edge behavior [interpolation per transform function for all CSS supported transform functions] (Issue #2684)
• Resolved: Make rotate with 3 values transition to a matrix and do matrix decomposition (Issue #2684)
• Resolved: Add these keywords [content-box and stroke-box] to transform-box property. (Issue #999)

Full Meeting Minutes

Minutes Berlin F2F 2018-04-12 Part II: CSS Tablets, Text L3, Overflow L3, CSS Contain, CSS 2.x, Testing

CSS Tables

• Resolved: Rename table-box to table-grid-box (Issue #2501)

Full Meeting Minutes || Spec Referenced

Text L3

• Resolved: Spaces don’t hang when break-spaces is specified (Issue #2465)
• Resolved: We should define what an alias is in CSS Cascade. (Issue #866)
• Resolved: We will make the required edits for the definition resolved previously. (Issue #866)
• Resolved: We create a new legacy shorthand concept in Cascade L4 for those things that we have legacy shorthands that should never be serialized. (Issue #866)
• Resolved: Everything that’s currently defined as an alias needs to use new legacy definition or is a legacy shorthand. (Issue #866)

Full Meeting Minutes || Spec Referenced

Overflow 3

• Resolved: Require that you leave space in scroll containers for block-end padding in the scrollable area. (Issue #129)
• Resolved: Undo the previous resolution and continue to figure out a whole model. (Issue #129)
• When discussing Issue #129 (padding-bottom in overflow content) the group originally thought they could solve the bigger author pain point (block-end padding) in isolation. However, as conversation continued it became clear that an entire modal that covered inline padding and the relationship to absolutely positioned elements was required to address this issue.

Full Meeting Minutes || Spec Referenced

CSS Contain

• Resolved: You’re allowed to have forced breaks inside a layout contained thing but you can’t propagate the break to the parent. (Issue #2527)
• Resolved: Elements with size containment are monolithic for the purpose of fragmentation. (Issue #2527)
• After the resolutions from the F2F are edited in the authors will request an updated CR publication.

Full Meeting Minutes || Spec Referenced

CSS 2.x

• Resolved: Accept this new editing process (documented here)
• Resolved: Use the naming scheme proposed at bottom of the proposal
• Resolved: Ask the team to make https://www.w3.org/TR/REC-CSS2 redirect to https://www.w3.org/TR/CSS2

Full Meeting Minutes || Spec Referenced

Testing

• The group discussed what it would take to move to WPT tests and, though there were plenty of pain points listed, the only commitment was from TabAtkins to continue improving bikeshed integration.
  • Some of the pain points mentioned:
    • Manual tests put a lot of pain on the tester
    • Ahem font not installed for Edge invalidates most of those results
    • Lack of controls over shared files to prevent breakage when changes are made
    • Not exporting tests in a way the test harness can import
    • Needs fuzzy matching for ref tests
    • No good way to flag/differentiate ‘may’ and ‘should’ tests from ‘must’
• Documentation for testing was also discussed (Issue #2438) and the group come up with several recommendations:
  • Use the testing wiki to guide new testers and browser vendors since the WPT documentation is too high level for that audience
  • Don’t re-write documentation that exists on WPT but instead link to it
  • Add search to the WPT documentation

Full Meeting Minutes

Minutes Berlin F2F 2018-04-12 Part I: Flexbox, Overflow, MultiCol, FX Specs Location, Publications and Editors, Grid 2, CSS Display

Flexbox

• Resolved: Accept the proposal to have width/height influence min-content contribution of shrinkable flex items (Issue #2353)

Full Meeting Minutes || Spec Referenced

CSS Overflow

• fantasai and florian introduced their proposal to create two new properties, max-lines and block-ellipsis, which combine into a shorthand line-clamp.
  • The goal of these properties is to serve as a replacement for -webkit-line-clamp while removing some of the behavior people don’t like thus allowing browsers to alias -webkit-line-clamp to line-clamp.
  • Generally this was favorably received though there were requests to add more examples and notes as well as to ensure that there won’t be breakage when an implementor switches from the current -webkit-line-clamp behavior to line-clamp.
  • An issue will be opened to ensure that the extension path for these features is clear before this can go into a full WD.
  • Resolved: Continue this work in Overflow as an ED
• Resolved: Copy text-overflow from UI3 to overflow-3, move text-overflow from UI4 to overflow-4.
• Resolved: Having max-lines not apply across BFC boundaries (Issue #2429)

Full Meeting Minutes || Spec Referenced

MultiCol

• Resolved: Have rachelandrew make the change to refer to fragmentation in general instead of paged media specifically. (Issue #1746)
• Resolved: Move this issue (Add switch to avoid generating empty column boxes?) to L2. (Issue #1565)
• Resolved: Won’t change [in reference to height of column rule] (Issue #2309)
• Resolved: No change to L1 [for spanning elements late in the content] refiled against L2 to think about in context of n-spanners (Issue #2448)
• Resolved: Go with option 1 in this sizing issue- overflow columns effect the multicol container’s height. (Issue #1745)
• Resolved: Accept the proposed text in Issue #2549 [In continuous media, this property (balancing) does not have any effect when there are overflow columns]
• Resolved: Publish a new working draft of multicol

Full Meeting Minutes || Spec Referenced

FX Specs Location

• When there are FXTF issues that need WG review, an email will be sent to the CSSWG mailing list.

Full Meeting Minutes

Publications and Editors

• Resolved: New WD for Filter Effects.
• krit will create a DoC for Masking so that it can be republished.
• Resolved: Add ChrisL and smfr as editors to Compositing and Blending
• Resolved: Editors for Geometry are krit and TabAtkins

Full Meeting Minutes

CSS Grid 2

• Resolved: Remove the duel-axis proposal. (Issue #2280)
• Resolved: Publish a new WD of Grid L2 with the removed duel-axis proposal.

Full Meeting Minutes || Spec Referenced

CSS Display

• Resolved: ::marker exists on all elements, on ::before and on ::after but no box unless it’s display: list-item. (Issue #1793)
• Resolved: In a block-in-inline split, the block is inside the inline in the box tree, and is a sibling of the two fragments of the inline in the fragment tree. (Issue #1477)
• Resolved: A multicolumn spanner that splits and inline is inside of the inline box tree and a sibling to the fragment in the fragment tree. (Issue #1477)

Full Meeting Minutes || Spec Referenced

Minutes Berlin F2F 2018-04-11 Part II: CSS Scoll Snap, CSS Text 3, Web Animations, CSS Fonts, CSS Text & Text Decoration, Ruby

CSS Scroll-Snap

• The group agreed that the focus should be encouraging users to reference the new version of Scroll Snap and that writing a guide to what can be done in both old and new would not move toward that goal (Issue #2523)

Full Meeting Minutes || Spec Referenced

CSS Text 3

• Resolved: Defer this (word-break:break-word) to next level. (Issue #2390)
• Resolved: Normatively state that text-transform does not apply to plaintext paste. (Issue #627)
• Resolved: Make text indent percentage relative to the content box of the element. (Issue #2394)
• Resolved: Requiring language for hyphenation to take effect. (Issue #869)
• Resolved: Treat lone CRs as 0 width spaces. (Issue #855)
• Resolved: Define hanging punctuation as scrollable overflow in all cases. (Issue #2398)
• The group needed more time to look at current behavior for Issue #1597 (intrinsically-sized box with text-indent) so it will be covered on a telecon.
• Resolved: Clarify spec to say control characters should be always visible even if fonts don’t provide a glyph. (Issue #1990)
• Resolved: Defer this (font-relative letter-spacing) to text L4. (Issue #2165)
• Resolved: Keep rule to collapse white space through bidi formatting chars, don’t mark at risk. (Issue #2233)
• Resolved: Defer this (hanging-punctuation: last applying to colons and dashes) to L4. (Issue #2392)

Full Meeting Minutes || Spec Referenced

Web Animations

• Implementations are in progress for Animations and there were several pieces of implementor feedback discussed.
  • The spec naming around timelines are currently all about time, but there’s interest in having it more about progress. However, it may be too late to change due to implementations that have shipped.
  • Querying the main thread for state will be similar to how threaded scrolling.
  • In Level 2 there is interest in exposing a web animation api to be used by javascript objects.
  • The focus of Level 2 will be to offer extension points to the core specified in Level 1.
• UA must implement coalescing for forward filling animations (Issue #2054)
• Most people felt that returning the longhand to getKeyframes would be sufficient, though doing better would be nice.
• Issue #2359 (Clarification about “make animation’s start time unresolved”) came from misreading of the spec, but raised a different problem that setTiming doesn’t do invalidation so a separate github will be opened.
• There’s a desire to have a timeline attached to a media source but there are several possible solutions that need to be evaluated.

Full Meeting Minutes || Spec Referenced

Fonts

• Resolved: Parse the value of src throwing out invalid parts like media queries and not like selectors. aka You split on the commas and throw out the pieces you don’t understand not the whole thing. (Issue #633)
• Resolved: Use this: format(string[supports feature-name#]?) where feature-name is a CSS-defined identifier. (Issue #633)
• An issue will be opened to determine if @supports for color fonts is necessary.
• Resolved: Add an auto keyword to the appropriate font descriptors that has the effect of the following: 1) for font selection purposes the font is selected as if the appropriate initial value is chosen. 2) for variation axis clamping, clamping does not occur. (Issue #2485)
• Resolved: Leave font-style computed values as-is; change font-style animation behavior so that ‘normal’ can animate with ‘oblique num’ (Issue #2505)
• Resolved: Use 14 degrees as the angle for undefined oblique. (Issue #2295)
• Resolved: Defer font-variant descriptor to L4. (Issue #2531)

Full Meeting Minutes || Spec Referenced

CSS Text & Text Decoration

• Resolved: Use from-font [for text decoration metrics] (Issue #2376)
• Resolved: Add this value [text-spacing:space-first], suggest it’s the default in epubs and add a open issue wondering if should be in the web in general. (Issue #2462)
• There was general consensus that the property for paragraph-level line breaking should be a modifier on wrap not a separate keyword, but the name still needs to be bikesheded. (Issue #672)

Full Meeting Minutes || Specs Referenced: CSS Text, CSS Text Decoration

Ruby

• Florian gave a brief introduction to the document of Ruby recommendations from Kobayashi-sensei. The document is available here and would be a good guide to Ruby editors.

Full Meeting Minutes || Spec Referenced

Minutes Berlin F2F 2018-04-11 Part I: CSS Contain, CSS Scoping, CSS Pseudo Elements, CSSOM, CSS UI 4, CSS Timing

CSS Contain

• Resolved: Align ‘contain:paint’ to ‘overflow:clip’ behavior. (Issue #2223)
• Resolved: Size layout and paint containment don’t apply to internal ruby elements. (Issue #2512)
• Resolved: Size containment does not apply to non-atomic inlines. (Issue #2510)
• Resolved: Clarify the definition of what and how an FC is created. (Issue #1457)
• Resolved: Layout and paint containment does not apply to non-atomic inlines. (Issue #1457)
• Resolved: No change to spec, but add examples and improve wording to clarify desired behavior. (Issue #2483)
• Resolved: Add this clarification to the spec. (Issue #2349)
• There’s only one open issue left to resolve (Issue #2527: How do layout and size containment interact with column/page fragmentation?). After that is closed the spec can be republished.

Full Meeting Minutes || Spec Referenced

CSS Scoping

• Resolved: Accept proposal in Issue #2158 (keep ::slotted and :host to a single argument)
• Resolved: Account for the specificity of the selector item and change the spec to say pseudo elements have same specificity of pseudo classes. (Issue #1915)

Full Meeting Minutes || Spec Referenced

CSS Pseudo Elements

• Resolved: ::selection is cleared for shipping unprefixed even though multiple implementations do not (yet) follow the spec. (Issue #2474)
• Resolved: Switch to using inheritance instead of cascade (to describe ::selection of a child). (Issue #2474)

Full Meeting Minutes || Spec Referenced

CSSOM

• Resolved: For elements not part of a tree or part of a detached tree they return no computed styles (and by no computed styles, we mean empty strings). (Issue #1548)
• Resolved: Elements not part of a flat tree return no style for getComputedStyle. (Issue #1548)
• Resolved: Regardless of what window you obtain the getComputedStyle function from the origin of the style is where ever the element is. (Issue #1548)
• Resolved: getComputedStyle returns none for elements part of non-rendered iframes. (Issue #1548)
• Resolved: getComputedStyle for pseudo elements that are not ::slotted (or similar future things) is supported. (Issue #2139)
• Resolved: Throw on invalid pseudo elements. (Issue #2139)
• Resolved: Add emilio as an editor of CSSOM.

Full Meeting Minutes || Spec Referenced

CSS UI 4

• Resolved: Add input-security: auto|none in UI 4 and applies to input type=password only. (Issue #2495)
• The group decided to restrict only to input type=password for now, but intentionally picked the name input-security so that this property can be later extended to other input types if necessary.

Full Meeting Minutes || Spec Referenced

CSS Timing

• Resolved: Have keywords be jump-start, jump-end, jump-none, jump-both (Issue #1680)

Full Meeting Minutes || Spec Referenced

Minutes Telecon 2018-06-06

• Resolved: Accept the suggestion in the issue plus a prefix for unless otherwise specified. Edits to be added UI 4 (Issue #2664).
• Resolved: Accept proposal in Issue #1432.
  • Proposal:
    • justify-content on the static position containing block is start, use the start edge of the static position containing block and the end edge of the actual containing block (as CSS2.1 requires).
    • If justify-content on the static position containing block is end, use the start edge of the actual containing block and the end edge of the static position containing block.
    • If justify-content on the static position containing block is center, use the start edge and end edges of the static position containing block.
• Resolved: Allow calc to handle negative 0s (Issue #545).
• Resolved: Close this issue (Issue #2546) by adding a note mentioning the difference between line box and other boxes.
• Resolved: Reserve “- -” for future use and it is not a valid custom property name. (Issue #2692).
• dbaron created a proposal for issue #2717 (anything that creates a stacking context should sort in the positioned descendants z-ordering list ). The working group needed time to review and will discuss again during a future meeting (perhaps the next F2F).
• No one was objecting to the purely syntactic nesting proposal TabAtkins had written for CSS Nesting however the call was running out of time so the group will revisit next week to ensure everyone has time to look. (Issue #2701)

Full Meeting Minutes

Older articles »

Archives

Search for:

Browse by date:

• July 2018 (2)
• June 2018 (8)
• May 2018 (9)
• April 2018 (5)
• March 2018 (6)
• February 2018 (2)
• January 2018 (3)
• December 2017 (9)
• November 2017 (2)
• October 2017 (4)
• September 2017 (5)
• August 2017 (7)
• July 2017 (6)
• June 2017 (4)
• May 2017 (3)
• April 2017 (2)
• March 2017 (6)
• February 2017 (16)
• January 2017 (2)
• December 2016 (4)
• November 2016 (5)
• October 2016 (4)
• September 2016 (3)
• August 2016 (4)
• July 2016 (4)
• June 2016 (14)
• May 2016 (6)
• April 2016 (7)
• March 2016 (10)
• February 2016 (1)
• January 2016 (7)
• December 2015 (5)
• November 2015 (3)
• October 2015 (3)
• September 2015 (16)
• August 2015 (3)
• July 2015 (6)
• June 2015 (11)
• May 2015 (7)
• April 2015 (6)
• March 2015 (6)
• February 2015 (2)
• January 2015 (7)
• December 2014 (6)
• November 2014 (3)
• October 2014 (10)
• September 2014 (4)
• August 2014 (2)
• July 2014 (4)
• June 2014 (8)
• May 2014 (5)
• April 2014 (5)
• March 2014 (8)
• February 2014 (14)
• January 2014 (5)
• December 2013 (3)
• November 2013 (6)
• October 2013 (12)
• September 2013 (5)
• August 2013 (5)
• July 2013 (14)
• June 2013 (4)
• May 2013 (8)
• April 2013 (8)
• March 2013 (9)
• February 2013 (6)
• January 2013 (7)
• December 2012 (6)
• November 2012 (9)
• October 2012 (8)
• September 2012 (1)
• August 2012 (17)
• July 2012 (2)
• June 2012 (6)
• May 2012 (11)
• April 2012 (9)
• March 2012 (8)
• February 2012 (7)
• January 2012 (5)
• December 2011 (13)
• November 2011 (1)
• October 2011 (5)
• September 2011 (8)
• August 2011 (17)
• July 2011 (2)
• June 2011 (6)
• May 2011 (7)
• April 2011 (4)
• March 2011 (6)
• February 2011 (6)
• January 2011 (4)
• December 2010 (3)
• November 2010 (8)
• October 2010 (8)
• September 2010 (4)
• August 2010 (3)
• July 2010 (5)
• June 2010 (6)
• May 2010 (4)
• April 2010 (6)
• March 2010 (3)
• February 2010 (5)
• January 2010 (5)
• December 2009 (4)
• November 2009 (2)
• October 2009 (6)
• September 2009 (3)
• August 2009 (3)
• July 2009 (4)
• June 2009 (11)
• March 2009 (9)
• February 2009 (4)
• January 2009 (3)
• November 2008 (8)
• October 2008 (3)
• September 2008 (6)
• August 2008 (1)
• July 2008 (4)
• June 2008 (4)
• May 2008 (4)
• April 2008 (10)
• March 2008 (3)
• February 2008 (3)
• January 2008 (2)
• December 2007 (7)
• November 2007 (8)
• October 2007 (3)
• September 2007 (5)
• August 2007 (3)
• July 2007 (4)
• May 2007 (1)

Browse by category:

• Best Practices (1)
• Feedback (2)
• general (30)
• i18n (2)
• publications (151)
• resolutions (572)
• testing (2)
• Uncategorized (9)

Site navigation

• 
• CSS home
• Learn & use
• Soft­ware
• Par­tic­i­pate / drafts
• 

Contact: Bert Bos
Copyright © 2017 W3C^®

Last updated 2018-07-19 09:12:39.000000