Minutes Telecon 2023-03-01
- The group was positive about the simplification proposed in FXTF Issue #363 (The description of contain flag in ray() function). They would like to make sure that folks who are expert in watch design are involved and then bring the issue back when the spec text is written.
- Resolved: Accept restrictions in this github comment with exception of :is and :where (Issue #8174: Add pseudo-class to establish before-change style for css-transitions on new elements)
- Resolved: Adopt this feature as overflow-bikeshed [name is to be decided later] (Issue #8361: Add method to prevent elements from contributing to scrollable overflow)
- Resolved: Accept this behavior for baseline-source:first|last (Issue #8214: baseline-source:first and overflow:hidden inline-boxes)
- Resolved: leading-trim: normal; >> text-box-trim: none; AND text-edge >> text-box-edge (Issue #8067: Naming Stuff)
- On the call there was a possible solution raised for issue #8286 (Making a stickypos in a scroller also see the viewport edges) to use overflow:clip so it’s explicitly not scrollable. Initial reaction was that that could work, but discussion will return to github to investigate further
Full Meeting Minutes
Minutes Scoping Breakout 2023-03-01
- Resolved: Close the issue as no-change (Issue #7943: change lower boundary keyword for @scope to “until”)
- Resolved: Accept clarifications for scoping selectors proposed by miriam (Issue #8377: Scoped selectors shouldn’t match the scope root unless explicitly requested with :scope?)
- Resolved: The specificity of the scope root is not applied to selectors from scoped rules (Issue #8500: The specificity of a scope rule)
- The examples and developer feedback for issue #6790 (Strong vs weak scoping proximity) were arguments for weak proximity. The group members looking for strong proximity are asked to add use cases into the spec over the next week so the working group can further discuss and reach a resolution.
Full Meeting Minutes
Minutes Telecon 2023-02-22
- Resolved: content-visibility: auto forces contain-intrinsic-size to gain an auto value, and we’ll define that auto value for contain-intrinsic-size so it works with all the current values, and then make sure that the last remembered size is forgotten when contain-intrinsic-size changes (specifying where in rendering step it happens) so we can deal with the cases that Rob brought up. (Issue #8407: Behavior of slightly offscreen content having `content-visibility:auto` and `contain-intrinsic-size` when UA margin around the viewport is 0)
- Resolved: Rename `text-space-collapse` back to `white-space-collapse` (Issue #8273: Renaming text-space-* to white-space-*)
- Resolved: outline-style: auto outlines, if influenced by an author color, are influenced by outline-color, which itself gets a new initial value keyword ‘auto’ which computes to ‘currentColor’ when outline-style is not auto and otherwise represents the ‘accent-color’ (Issue #7761: Tweaking outline-style: auto colors)
- Tests will be run to define exactly what implementations do currently for issue #7700 (Align canonical order of `outline` sub-properties with `border`) to help drive a resolution.
Full Meeting Minutes
Minutes Telecon 2023-02-15
- The team will have multiple two hour calls over several weeks in lieu of a F2F.
- Resolved: stickypos makes a stacking context, just like fixpos (Issue #1053: position:sticky should create a stacking context)
- Resolved: Clarify that due to the box-tree re-parenting, an ancestor outside the dialog can’t be a fixpos CB for descendants of the dialog (Issue #8040: Containing block of dialog fixed position children)
- Diagrams and demos will be added to issue #8040 to help resolve what exactly is the CB of a fixpos descendant of the dialog.
- Resolved: Publish new WD of Position 3 and Align 3
- The group reviewed argyle’s proposal for issue #7937 (Let’s finally settle contrast-color() syntax). There were parts that team members were interested in exploring more such as having short keywords to give some reasonable defaults. The proposal would not allow for multiple algorithms which could be necessary to accommodate the current wcag requirements. There’s a desire to explore the syntax further as well as other functional algorithms.
Full Meeting Minutes
Minutes Telecon 2023-02-08
- Resolved: Remove contain:layout requirement for view-transition to work (Issue #8139: Clarify rendering constraints for elements participating in a transition)
- Resolved: A non-none view-transition-name acts similar to a non-1 opacity (stacking context, grouping element, backdrop root) (Issue #8139)
- Resolved: Publish FPWD of anchor-position; Tab will send that request
- Resolved: Add Relative Color Syntax from CSS Color 5 to Safe to Release pre-CR Exceptions (Issue #7883: Start on CSS Snapshot 2023)
- Resolved: Add conditional-4 and cascade-5 to the rough-interop list (Issue #7883)
- Resolved: Publish 2023 Snapshot (after resolutions edited) (Issue #7883)
- Resolved: Chris Lilley is added to Snapshot editor list (Issue #7883)
- Resolved: Add scroll-snap-1 to rough-interop list (Issue #7883)
- Resolved: Accept Chris’s edits (Issue #7870: Serialization of named colors)
- Resolved: non-RCS rgb() and hsl() can mix numbers/%s when using the modern syntax (space and slash, not comma) (Issue #7900: gba()` is legacy so does not support `none`. Right?)
- The group reviewed the options for what color-contrast would composite the background against (Issue #7358: color-contrast() should take transparency into account) but did not have clear agreement on the best approach before running out of time.
Full Meeting Minutes
Minutes Telecon 2023-02-01
- Resolved: Accept the proposal in the issue (initial value is space-first, and hanging-punctuation hangs ideographic space) (Issue #2462: Propose ‘text-spacing: space-first’ (trim-start-except-first-line) as a normal behavior)
- Resolved: Accept the proposal in the issue to split text-spacing into longhands (Issue #4246: text-spacing is very complicated)
- Resolved: Move line-clamp stuff from Overflow 3 to 4 (Issue #8271: Reshuffling levels)
- Resolved: Move the continue:fragments to an appendix, marking it as unstable (Issue #8271)
- Resolved: Publish Web Animations 2 as FPWD, with flackr and Brian as editors
- Resolved: Publish CSS Animations 2 FPWD
- Resolved: aspect-ratio queries are always true (except when it can’t apply at all) (Issue #8244: How to evaluate `ratio` queries?)
- Resolved: Accept Oriol’s option 1 (0/0 is comparable with itself, but false when compared with any other ratio) (Issue #8244)
Full Meeting Minutes
Minutes Telecon 2023-01-25
- Resolved: Publish updated WD of CSS Nesting with an added issue about lookahead
- Resolved: A single-string value changes what is inserted, but not where (Issue #2975: hyphenate-character doesn’t just put hyphen at end of line)
- Resolved: Close WONTFIX (Issue #5972: Hyphenation styling should apply to the wbr element)
- Resolved: Accept changes (Issue #5973: Better describe the likely outcomes of hyphenation (editorial))
- Resolved: Republish CR [of CSS Text 3]!
- Resolved: Restriction will be relaxed to allow punctuation-only matching (Issue #2254: Multi-line ::first-letter)
- Resolved: Revert previous resolution; accept :blank works for this use case (Issue #2517: Clarification: do ::placeholder/:placeholder-shown apply to `select`s’ “placeholder label option”?)
- Resolved: ::first-line applies to markers when `list-style-position` is `inside` but excludes them when it’s `outside` (Issue #5406: Should ::first-line include markers?)
- Resolved: CSS inline layout properties are not applied to ::placeholder (Issue #5379: Should `line-height` be applicable to ::placeholder?)
- Discussions began around use cases for issue #6641 (Custom properties on :root) but the call time ended before the group could do any deep discussion about the potential usage.
Full Meeting Minutes
Minutes Telecon 2023-01-18
- On the call there were two new options raised to address issue #7551 (Inconsistent handling of known and unknown features jeopardizes backward compatibility). The group wanted to add examples to evaluate the two options so discussion will return to GitHub. The options were:
- Each queried feature could evaluate to different container.
- Attempt to match the queries against each possible container. If the container *can* match a given query, good; if not, it evaluates to unknown.
- Resolved: Adopt suggested change to rename to `updateCallbackDone` (Issue #8144: domUpdated isn’t the right term)
- Discussion will return to github for issue #616 (Hyphenate only overflowing words?) to discuss if hyphenate-limit-zone could cover the use case.
- The initial thought was it would be possible to use justify-content instead of text-group but there was a need to confirm the compatibility before going that route (Issue #5703: Re-use justify-content instead of text-group align?).
Full Meeting Minutes
Minutes Telecon 2023-1-11
- Though the discussion on issue #8174 (Add pseudo-class to establish before-change style for css-transitions on new elements) had leaned toward adding a pseudo-element instead of a pseudo-class, there were concerns this was new ground for pseudo-elements. It was agreed that this should be a pseudo-class behaving more like :visited. A new proposal will be drafted and then this issue will be brought back to the group.
- The group discussed the proposal for entry and exit animations for top-layer elements (Issue #8189) and a few considerations were raised.
- The proposal needs to ensure that it doesn’t have the same problems as z-index.
- There was some uncertainty as to if this should apply to non-modal dialogs.
- Some concern was expressed that this only applied to transitions where authors may try and use it for other properties.
- Resolved: Accept Chris’s proposal [of text for resolving the RCS value when currentColor is the origin] (Issue #7978: Is relative color syntax ready to ship?)
- Resolved: Keywords with multiple specified types result in number (Issue #7876: Clarification on how `channel keywords` with multiple specified types work)
- Resolved: Adopt Option 3 (Issue #8249: Problem with mixing properties and selectors)
- A Nesting breakout will be scheduled next week to cover the outstanding objection to the above resolution as well as make additional progress on other Nesting issues.
Full Meeting Minutes
Minutes Telecon 2022-12-21
- The poll showed a clear preference for option 3 for the nesting syntax (Issue #8248: Choose Nesting syntax — Option 3, 4 or 5?). There were objections on the call that this solution’s mixing of selectors and properties will create future limitations on the language.
- Resolved: Reject options 4 and 5, go with option 3 with continuing refinement (Issue #8248: Choose Nesting syntax — Option 3, 4 or 5?)
- Resolved: Accept flackr’s fix [When setting the playback rate, skip step 4 (setting the current time to previous time) if has finite timeline (i.e. the timeline is scroll linked)] (Issue #2075: Don’t preserve current time for scroll linked animations when changing playbackRate)
- Resolved: Newly-discovered timelines trigger a new layout at the RO portion of the frame lifecycle. (Maybe other times, tbd.) (Issue #5261: Behavior of scroll-linked animations in the first frame)
Full Meeting Minutes