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
Minutes Telecon 2022-12-14
- The group will work on the issues raised with the editor’s draft for Masonry Layout before moving forward to FPWD (Issue #8195: FPWD for Masonry Layout)
- There are several open questions on issue #7808 (Firing observations on insert/remove when rendered size is (0, 0)) that need to be answered to reach resolution. Please engage in the issue so that the topic can move forward.
- Resolved: We will use an empty array when there are no fragments (Issue #7734: What should the fragment-aware behavior be when there are no fragments?)
- Issue #7734 will stay open while discussion continues on handling non-atomic inlines.
- Resolved: If internal parts of an svg are sliced we will return size before slicing (Issue #7736: Fragment-aware behavior for SVG?)
- Resolved: If a discretely animatable property is listed in a transition it will. By default the all keyword will not transition (Issue #4441: Start transitions on discrete animation types)
- A note will be added to the Transitions spec that we are considering a discrete keyword and ask authors for use cases to support an addition.
Full Meeting Minutes
Minutes Telecon 2022-12-07 Late Call
- Resolved: Accept the proposal (Issue #5653: Order of pause, setTimeline)
- proposal: set the timeline first, then pause, as the pause being applied in the same update as the new animation-timeline implies to me that it is meant to pause in the new timeline]
- Resolved: Animation events fire for scroll linked animations as defined by web animations spec (Issue #4324: Should animation events fire every time active range is left/reentered?)
- Resolved: Add auto as default value (Issue #6530: Should the initial value for animation-duration be auto?)
- Resolved: Have parsing with fixed order of name and axis (Issue #7627: `scroll-timeline` and `view-timeline` shorthand syntax)
- Resolved: Animation range and animation delay are separate things that compound (Issue #7901: What’s the point of animation-range?)
- Resolved: Add length % to animation-range to be used as offsets (Issue #7575: Bring back Scroll Offsets)
- Resolved: Scroll animation is inactive when denominator is 0 (Issue #7778: currentTime when scroll range is 0 (again))
Full Meeting Minutes
Minutes Telecon 2022-12-07 Early Call
- Resolved: Use set explicitly, reset implicitly and cascade implicitly terms (Issue #7832: Should `font-palette` be reset by the `font` shorthand?)
- Resolved: Put font-palette in the cascaded independently category (Issue #7832)
- Resolved: Explicitly enumerate all properties which are cascaded independently that start with font- (Issue #7832)
- Discussion on issue #4264 (Explicit anchoring) will return to github to discuss further if there’s a desire to keep improving the algorithm or if a preference should be introduced because the algorithm is pretty much complete.
- Resolved: Merge this PR (Pull request #8095: Define root element (as a term, and its display type))
- Resolved: Revert the definition of crisp edges to allow for more advanced algorithms (Issue #6038: Is “image-rendering: crisp-edges” still worthwhile to keep separate?)
- Resolved: Make :has unforgiving (Issue #7676: The forgiving nature of :has breaks jQuery when used with a complex :has selector)
- Resolved: Limit forgiving behavior to :is and :where and remove it everywhere else (Issue #7676)
- Resolved: Match intersection observer behavior for this definition (Issue #5641: Spec is unclear about whether 0-sized boxes can be “relevant to the user” (since they have zero intersection area))
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: