Minutes Telecon 2020-11-04
- Resolved: Close this issue as an editorial change (Issue #5663: Should definite cross size be used to compute flex item’s transferred size suggestion?)
- Resolved: Add an appendix to flexbox spec for the webkit prefix properties (Issue #5634: Move -webkit- prefixed aliases into flexbox?)
- Resolved: Add these to the appendix as MUST or MAY depending on implementation [web exposed implementations are a MUST, otherwise it’s a MAY] and SHOULD NOT for authors. Add details about how they’re not simple aliases (Issue #5634)
- Resolved: Uncomment possibility of an exception and accept the PR (PR #5643: Clarify how sizing containment works)
- The group agreed that allowing a browser to search content that is currently hidden when doing find-in-page and ScrollToTextFragment was a valuable use case to solve (Issue #5595: Proposal: content-visibility: hidden-matchable). Before reaching any resolution, though, there is a desire to explore further if there are other types of finding hidden content which should be included such as searching by text fragment ID. There also needs to be a review of the proposal to ensure that it will provide a good experience when it interacts with various accessibility tools.
- gregwhitworth will review PR #4150 (Remove SVG specific text) to see if it needs to be re-written.
- Resolved: Add an optional line in propdef table for logical property groups (Issue #2822: Spec should introduce propdef table notation for logical properties)
- There needs to be some additional exploration of use cases for issue #5650 (Add fill(length-percentage) / rename stretch keyword for width/height?) prior to a resolution. The group was leaning toward keeping the keyword name as ‘stretch’.
- Resolved: Interpolate ratios using logarithm (Issue #5953: How to interpolate ratio?)
Full Meeting Minutes
Minutes Telecon 2020-10-07
- The group will not have its regular call on the 21st of October due to other TPAC calls. If anyone thinks the 14th or 28th should also be cancelled please reach out on the private list.
- In order to make a decision on :blank (Issue #1967) more research is necessary on if :empty can ignore whitespace. chrishtr will help fantasai in getting a sample of pages to investigate if sites using whitespace in :empty are relying on the current behavior.
- There was wide interest in improving the interaction between scroll animations and prefers-reduced-motion (Issue #5321: TAG feedback: interaction with prefers reduced motion). There were some potential solutions that came out of the conversation:
- Have scroll animations move from their start state to their end state without the animation in the middle, perhaps with additional author controls to define some intermediate states
- Allow browsers to remove most scroll animations and rely on !important for authors to still have their animation when it was required.
- Don’t trigger the animation immediately. Instead, suspend the animation until the scroll action finishes, interpolate what state the animation should be in at that point in the scroll, and then display that state.
-
There is a need to experiment with the approaches to see which of them gives the best results. The Github issue will stay open for further conversation around experiments.
- Resolved: Add superscript and subscript descriptors using ‘normal’, percentages, and ‘from-font’ values (Issue #5518: @font-face overrides for superscript/subscript metrics)
- Resolved: Add target-text pseudo element (Issue #5522: Add a highlight pseudo-element for scroll-to-text)
- Resolved: Add these terms [rectangular edges vs edges that have had their corners shaped] but bikeshed names in GH issue (Issue #5132: How to refer to the corner-shaped padding/border/content edges)
- Resolved: For aliased properties, the general rule is both sides of the alias get new values as defined (Issue #4839: Issues with legacy name alias)
Full Meeting Minutes
Minutes Telecon 2020-09-30
- The request in issue #5480 (Should interoperability be a goal for the `accent-color` spec?) is to select between two approaches:
- The proposal for Option A is the full proposal. This includes the normative section, the Motivation and Intent section, and the non-normative examples section.
- The proposal for Option B is just the normative section, with the 4th paragraph referring to “interop” removed.
- There was also another proposal put forward in issue #5544 (make accent-color: color + a list of alternatives, not complements) which didn’t slot neatly into either Option A or Option B, though it was a bit closer to Option B.
- On the call there wasn’t clear agreement between Option A and Option B. Some of this was due to the new proposal and some due to a general desire to not be too vague or too specific but finding that hard to fit desire into the current binary choice. Discussion will continue on GitHub to further clarify that the Option A and Option B are not final selection of language but instead a general direction as well as how issue #5544 should be considered in this discussion.
- Resolved: scroll-snap overrides scroll-anchoring for behavior heuristics (Issue #4830: Clarify the interaction between snapping and scroll anchoring)
- Resolved: Close no change based on reasoning in Majid’s comment in issue #4037 (Compat between webkit and blink/gecko regarding “implicit” scroll boundary snap positions)
- Resolved: ‘auto’ value of quote to be based on parent language (Issue #5478: Quote character choice must depend on surrounding language, not language of the quotation)
- Resolved: Add ‘match-parent’ keyword [to quote property] (Issue #5478)
- Resolved: Colors assigned due to forced-colors mode are not interpolatable (Issue #5419: Clarify expectations re forced-color mode, system colors, and transitions)
- Resolved: Defer the behavior of discarding line breaks adjacent to ambiguous characters to L4 of css-text (Issue #5017: Discarding line breaks adjacent to ambiguous characters)
- iank is leading an effort to slowly see how much of the currently incompatible behavior for scrollable overflow (Issue #129: Clarify padding-bottom in overflow content) can be resolved in the way authors would expect without causing issues for web compatibility. The plan is to make incremental small changes over the next few months and then report the results back to the group.
Full Meeting Minutes
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.)
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: