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
« Previous article
Next article »