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
Minutes Telecon 2022-11-16
- There is still discussion necessary on issue #7306 (Move the definition of “display mode” back to Manifest spec) about if this should be generalized before a resolution can be reached.
- Resolved: Take second solution for this case. Update the last remembered size if element doesn’t skip its contents (Issue #7807: content-visibility: auto kinda broken by not using last remembered size with contain: size)
- Issue #3320 (Clarify fragment URLs resolve against the current tree, not document tree) needs more discussion about the motivation behind the behavior before a resolution can be reached.
- Resolved: Add this definition to values-4 and evaluate new definition against existing test suite (Issue #5210: Define when border rounding happens, and to which properties it applies)
- There was disagreement on the value changing fragmentation as proposed in issue #5648 (contain:size shouldn’t fragment as monolithic) as well as how common the use case will be once container queries are more common. Discussion will continue on github.
- Administrative:
- Upcoming meeting updates:
- The group will be meeting next week.
- Next long call is scheduled on Nov 30th.
- plinss gave an update on the server work done to add stability and what is left to do.
Full Meeting Minutes
Minutes Telecon 2022-11-09
- Upcoming meeting updates:
- Next long call is scheduled on Nov 30th.
- Please reply to the email on the private list about if we should cancel the week of 21 November (US Thanksgiving).
- jensimmons and fantasai are organizing a workshop next Monday on Inline Layout.
- Please add feedback and thoughts on the model to collaborate with TAG to the github issue (Issue #7835: Co-authoring CSS Design Principles with the TAG).
- Resolved: Publish css-shapes-1 CRD (Issue #6450: Updated CR of CSS Shapes? Administrative Tracker For external review/publication tracking issues)
- Resolved: Accept proposal (Issue #7956: Behaviour of the finished promise)
- Resolved: view-transition-image-pair [is the property name for the pseudo-element which adds isolation for blending] (Issue #7960: CSS selector keywords)
- Resolved: UA styles on the pseudo-DOM stay in sync with author DOM for any developer observable API (Issue #7812: When to update the pseudo element styles)
- Resolved: Elements under content-visibility:auto element that skip its contents are not eligible to participate in view transition (Issue #7874: content-visibility: auto elements are relevant to the user during a transition)
- Resolved: Change to present tense for ContentVisiblityAutoStateChanged (event and object) (Issue #7603: Incomplete event definition for ContentVisibilityAutoStateChanged)
Full Meeting Minutes
Minutes Telecon 2022-11-02
- The next long-form meeting will be November 30th starting a few hours before the normal meeting time.
- Resolved: We define the first baseline as the highest baseline in all the columns and spanners of the multicol (Issue #7856: First baseline of a multicol)
- Text will be added to Multicol to make sure we define that relpos doesn’t affect baseline alignment
- Resolved: Change the spec to simplify this sizing and figure out what tests we need (Issue #7465: How to properly accommodate margin/border/padding of a subgrid with no item on the edges)
- Resolved: Take the changes listed in this comment (Issue #7612: *-items properties might need to resolve directions early)
- Resolved: Use the writing mode of the parent’s formatting context for staticpos (Issue #7599: align-self / justify-self on abspos elements isn’t back compatible?)
- Resolved: Align justify axis of non staticpos use writing mode of their containing block (Issue #7599)
- The recommendation for issue #3052 (Investigate applying align-content to single-line flex containers) is to close no change based on use counter data from Chromium. Before resolving to close fantasai will verify that accepting the proposal would cause a different to a sample of the sites found in the use counter.
- Resolved: Add a SHOULD requirement for considering the filter effect extent and interaction with UA margin (Issue #7711: filter effects and “relevant to the user”)
- Resolved: Accept the proposed resolutions for items 1, 2, 3, 5, & 6 (Issue #7960: CSS selector keywords)
- Property used on DOM elements to tag them for independent animations: view-transition-name
- The pseudo-element which directly originates from the root element and is the ancestor for all container elements: html::view-transition
- The pseudo-element which animates the size and position for tagged elements: html::view-transition-group(*)
- The pseudo-element which displays snapshot from the old DOM element: html::view-transition-old(*)
- The pseudo-element which displays snapshot from the new DOM element: html::view-transition-new(*)
Full Meeting Minutes
Minutes Extended Telecon 2022-10-26
Publications
View Transitions
- Resolved: Use “snapshot viewport” for root element snapshot and UA CSS to size and position ::page-transition at snapshot viewport (Issue #7859: Define transitions over changing viewport)
- Resolved: ake khushal’s proposal to use pseudo-element syntax for view transitions (Issue #7928: Using pseudo-elements vs shadow DOM syntax)
- Resolved: Go with the Option 3 syntax (Issue #7788: CSS selector syntax for generated elements and API names). [Option 3: we select this as if they are all children of html:html::view-transition, html::view-transition-old(foo), etc]
- Resolved: Name the function .startViewTransition() (Issue #7788)
- Resolved: Synchronously generate styles for pseudo-DOM after DomUpdateCallback and before resolving ready promise (Issue #7812: When to update pseudo-element styles)
- Resolved: Update the UA stylesheet as needed in a new step after the current step 14 of “update the rendering” (after RO callbacks are done) (Issue #7812)
Nesting
- Resolved: Allow relative selectors for both nesting and @scope (Issue #7854: Allow relative selector syntax in @nest rules)
- The group revisited the four proposals to address issue #7834 (Syntax Invites Errors) which are detailed in the spec.
- The original debate was between options 1 and 3 and in the last conversation there was also discussion that option 4 may get better results. Discussion first focused on option 1 vs 3.
- Resolved: We’re taking option 3 over option 1 (Issue #7834)
- It was not clear if option 3 or 4 was better and more examples need to be added as well as further developer engagement around this pair of options.
- Resolved: Change the spec to reflect option 3 (Issue #7834)
- Resolved: Open issue for further discussion of 3 vs 4 (Issue #7834)
Full Meeting Minutes Part I and Part II
![[Photo: group photo of the CSS working group in San Francisco]](/web/20230119215856im_/https://www.w3.org/Style/CSS/csswg-2016.jpg)
Contact: