Minutes Telecon 2020-09-23
- Resolved: Change the spec to match current web behavior so fallback content is not matched by
::slotted (Issue #5482: Consider aligning ::slotted() for fallback content with implementations)
- Resolved: Add more examples to this section of the spec (Issue #5482)
- In discussing issue #5480 (Should interoperability be a goal for the `accent-color` spec?) there were two viewpoints to consider; implementors and authors.
- From an implementor point of view there were still concerns expressed about the implementability of the accent-color property. It’s important to continue allowing browsers to ignore accent-colors if necessary.
- From an author point of view this spec should be understood as allowing them to provide browsers a hint as to the colors they prefer. Providing that hint does require a level of interoperability where similar form elements display the accent-color similarly so authors can ensure proper contrast.
- There was general agreement that if we’re doing an accent-color property there does need to be examples in a non-normative section which gives guidance and will allow authors to have some consistency in usage. However, there wasn’t broad agreement that the non-normative section as written was what the group wanted to resolve on so discussion will go back to github with a request for specific feedback on how to improve the text for the non-normative examples in the spec.
Full Meeting Minutes
Minutes Telecon 2020-09-16
- In addition to the planned meetings with the Internationalization and ACR/Accessibility groups there is a desire to meet with the Open UI community group. Rossen, gregwhitworth, and astearns will coordinate on a time.
- Resolved: Have the logical value of resize be that of the element itself (Issue #3281: Mapping of logical values in ‘resize’)
- Resolved: Treat CR as an ordinary space (Issue #5410: Reconsider the resolution on #855)
- Resolved: Add ascent, descent, and line-gap override as fontface descriptors that take percentages (Issue #4792: Interoperable font metrics)
- New issues need to be opened for some of the other descriptors raised in issue #4792. One would be to further explore the proposal for advance-override and the other would be to evaluate handling the superscript and subscript values with a similar override.
- Before issue #4430 (Proposal to extend CSS font-optical-sizing) can reach a resolution there needs to be more discussion and research into how the various pixel and point conversions are handled when moving between print and digital displays.
Full Meeting Minutes
Minutes Math Telecon 2020-09-10
- Issue #5384 (MathML Core related CSS) provides a meta summary of what the team is trying to achieve with the MathML specification. Much of this work has been done in Chromium and is ready to be reviewed and altered based on author feedback. Both Gecko and WebKit have some done as well behind flags.
- Resolved: Add ‘math’ as a ‘display-inside’ value. (Issue #5385: math/inline-math)
- Resolved: Add ‘inline-math’ as a ‘display-legacy’ value. (Issue #5385)
- Resolved: ‘math’ outside of MathML context behaves as ‘flow’ (Issue #5385)
- Resolved: ‘math’ outside of MathML context computes to ‘flow’ (Issue #5385)
- A separate issue will be filed to discuss how to handle a non-MathML element inside a MathML element.
- Resolved: Add ‘math-auto’ to text-transform (Issue #5386: text-transform values for MathML)
- There wasn’t agreement on the other text-transform values in issue #5386 based on some concerns about both the quantity of new values and how they will interact with screenreaders. Discussion will continue on github.
- Resolved: Add math-style: normal | compact (Issue #5387: math style (minimizing logical height of an equation))
Full Meeting Minutes
Minutes Telecon 2020-09-09
- Resolved: Add chris and fantasai as editors to CSS Conditional 3 (Issue #5315: Let’s finish the specification)
- Though they seem similar the discussion find-in-page and scroll-to-text needs to be separated into two issues (Issue #5233: Add a highlight pseudo-element for find-in-page or scroll-to-text).
- There were concerns that find-in-page may be a mis-match with the highlight pseudo elements because several browsers have additional styling.
- The original developer request was to style scroll-to-text but there are use cases for both properties that should be documented.
- Resolved: We’re interested and would like chrishtr to pursue and come back with proposal text [for find-in-page and scroll-to-text] (Issue #5233)
- Resolved: Continue working on standardizing these 3 pseudos (::range-thumb, ::range-track, ::range-progress) (Issue #4410: Standardizing input[type=”range”] styling)
- There’s interest in having a joint meeting with OpenUI to discuss the more holistic approach to defining parts of controls that they’re working on.
- Resolved: Change the spec to say tab-size applies to inlines but when that happens the number values apply to advance width from block container (Issue #5489: ‘tab-size’ de facto applies to inline boxes)
Full Meeting Minutes
Minutes Telecon 2020-09-02
- Resolved: Move forward with Cascade L3 REC without retesting CSS 2 tests (Issue #5296: Publish Cascading and Inheritance 3 as a REC)
- The group is still committed to having better error recovery for :is() and TabAtkins will get the edits into the spec (Issue #3264: Let :is() have better error-recovery behavior than normal Selectors)
- Resolved: forced-colors does not override border-image (Issue #5469: Should forced-colors override `border-image`?)
- TabAtkins added spec language to have image set discriminate on format. The group prefers having the image-set use a type() function and therefore be similar to HTML.
- Resolved: Republish Images 4
- Resolved: Do not inherit scrollbar-gutter by default (Issue #5231: scrollbar-gutter should not be inherited)
- Resolved: Disallow animation-tainted substitutions in any non-animatable property (Issue #5341)
- Resolved: Using initial value as fallback of var triggers initial value behavior assuming that the property only has that keyword because of substitution (Issue #5325: CSS-wide keywords in fallbacks)
- TabAtkins is compiling the changes list and will be asking for a new publication of Variables shortly.
- Resolved: Accept the proposed text (Issue #5237: leading-trim through to descendant line boxes)
- Resolved: Rename the property from ‘leading-trim’ to ‘trim-leading’ (Issue #5237)
- Resolved: Rename fetch() to src() (Issue #541: Add url() alias that does not accept unquoted URLs)
Full Meeting Minutes
Minutes Telecon 2020-08-26
- The proposal for accent-color was updated after last week’s discussion to include multiple examples of each form control. The current proposal’s goal is to encourage all implementations to have the same definition of what part of a form control is the accent color given a similar layout but when creating a new layout implementors are free to create a new definition for the a new design while following the spirit of the requirements. The main concern about is that the proposed level of guidance to standardize will limit the ability to innovate and isn’t necessary given the further level of control over form controls being designed in the OpenUI project. The two viewpoints will need to be balanced to make sure that developers have enough control that they’ll use the property but not prevent implementors from being able to iterate on their form controls. The items which still require discussion will be broken into separate github issues in order to create more focused conversations.
- Resolved: The group wants to add accent-color and discussion on details will continue (Issue #5187: Allow specifying the “accent color” of a form control element)
- Resolved: Move this proposal into the spec (Issue #4470: Custom Cascade Layers (formerly “custom origins”))
- Resolved: Publish new WD of CSS Inline
Full Meeting Minutes
CSS Cascading and Inheritance Level 4 Returned to WD
The CSS Working Group is returning CSS Cascading and Inheritance Level 4 to Working Draft status in order to incorporate the cascading and inheritance rules pertaining to Shadow DOM. Also to drop scoped styles (again) due to lack of interest from implementers. (An update to CSS Cascading and Inheritance Level 3 has also been published to keep editorial fixes in sync.)
CSS Cascading and Inheritance 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). Changes since the previous Candidate Recommendation are listed in the Changes section.
This is a Last Call for Comments; the CSSWG expects to return the module to CR soon. We are requesting comments, or alternately a request for extended time, by 20 September 2020.
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-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.)
CSS Grid Layout Level 2 (Subgrid) Candidate Recommendation
The CSS Working Group has published a Candidate Recommendation and invites implementations of CSS CSS Grid Layout Level 2. This module defines a layout manager, the grid, which makes it easy to specify complex, responsive 2-dimensional layouts for a page or sub-component of the page. Level 2 introduces the “subgrid” feature that was cut from Level 1 due to lack of implementations, and which allows sharing grid lines across nested markup.
There have been no changes since the previous Working Draft other than incorporating the full text of CSS Grid Layout Level 1; and all new features other than subgrid have been deferred to Level 3.
The editors are grateful to Mozilla for implementing and giving feedback, and encourage other CSS implementations to update so that authors and users can benefit from subgrid’s ability to combine content-sized grid layouts with nested structural markup.
Feedback can be sent 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-grid-2]) and your comment topic in the subject line.
CSS Grid Layout Level 1 Revision 3
The CSS Working Group has published an updated Candidate Recommendation 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 sub-component of the page.
This update addresses most of the feedback received since the December 2017 CR, including almost all of the known errors; there remain a number of issues relating to improvements to track sizing algorithm that will be addressed in the next revision. The changes consist mostly of slight adjustments to the grid sizing algorithm and a few fixes to things like serialization. All significant since the last Working Draft are listed (with diffs) in the Changes section, and a Disposition of Comments (102 issues) is available.
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-grid-1]) 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 2020-08-19
- Resolved: Reject proposal, no change to semicolons (Issue #5413: Voluntary semicolons)
- Implementors are requested to review the proposal to alter how ratio-constrained elements are sized in definite-sized Grid/Flexbox containers (Issue #5317). The proposal is to contain-fit the image into the available space instead of the current behavior in the spec which is to calculate its max-content size using the inline axis of the containing block.
- Resolved: System colors will be accepted as specified, everything else is forced (Issue #4178: More granular overriding of forced colors mode than per-element)
- In response to the working group’s request for a more detailed proposal a possible spec was written for review (Issue #5187: Allow specifying the “accent color” of a form control element).
- The general approach to let an author define what the accent color should be and then additional colors was generally accepted.
- The proposal has a mapping for each form control to which color is ‘primary’ and which is ‘contrasting’. There is a request to have more examples of each form control including historic designs to make sure the mapping holds up. There was also a question about how gradients would be handled.
- The biggest concern expressed is that being too exact in the definition will limit future variations on form controls. The proposal was written to be extensible but the exact mapping may still impose constraints. There will need to be a balance between defining too much and creating limitations in the future versus defining too little and having authors not want to use the property or everyone have to conform to the first implementation.
- There wasn’t time on the call to develop next steps for this proposal so it will be at the top of next week’s agenda.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: