[css-2023] Finish up CSS Snapshot 2023

[SebastianZ]

As the year is slowly coming to an end, the 2023 snapshot should be wrapped up and published soon.

While there were a lot of spec. updates this year, it seems to me there was one that's fairly stable now, which is CSS View Transitions Level 1.

CSS Scroll Snap Level 1 should probably be removed from the "Fairly Stable" section because it's already in the "Rough Interoperability" section.

Other specs which were part of the Interop 2023 project might be added as well to the "Rough Interoperability" section. Though that still needs to be checked.

Sebastian

[svgeesus]

Agreed, View Transitions 1 is a CR Snapshot and the test results show a single implementation doing well.

[svgeesus]

CSS Scroll Snap Level 1 should probably be removed from the "Fairly Stable" section because it's already in the "Rough Interoperability" section.

Good catch, fixed

Edit: I didn't notice when responding that @SebastianZ had mixed up the stability order of "Fairly Stable" and "Rough Interoperability", see my later comment.

[svgeesus]

@tabatkins @khushalsagar @jakearchibald thoughts on moving View Transitions 1 to "fairly stable"?

[khushalsagar]

Yea, that sounds good to me.

We had 3 minor issues resolved since the last CR snapshot, I've sent a PR for them : #9575. Let me know if you need an up-to-date CR snapshot before making this switch.

[svgeesus]

@khushalsagar I merged your PR. As editor, you can commit directly on isses with consensus and resolved discussion.

In terms of updating your spec, that would be a CR Draft and just requires a CSSWG resolution. You can propose an async resolution for stuff like that. However, the snapshot probably won't be published until the end of this year so don't wait for that. And moving specs withing the various buckets of the snapshot requires a CSSWG resolution, too.

[SebastianZ]

CSS Scroll Snap Level 1 should probably be removed from the "Fairly Stable" section because it's already in the "Rough Interoperability" section.

Good catch, fixed

Should have been the other way round, i.e. it should be in the "Rough Interoperability" section as we have an interoperability of ~96% according to WPT.

Sebastian

[SebastianZ]

Adding this to the agenda as the end of the year is approaching.

Topics to discuss:

• Add CSS View Transitions 1 to the "Fairly Stable" section
• Any other specs to add?
• Publish as Group Note
• Aside: Also publish CSS 2022 as Group Note (currently still Group Draft Note)

Sebastian

[css-meeting-bot]

The CSS Working Group just discussed [css-2023] Finish up CSS Snapshot 2023, and agreed to the following:

• RESOLVED: only change is the snapshot to record today is add css-view-transitions-1 to fairly stable
• RESOLVED: publish snapshot 2023 with css-view-transitions moving to fairly stable and css-scroll-snap moving to rough interoperability
• RESOLVED: Republish snapshot 2022 as Group Note (not Draft Note)

The full IRC log of that discussion

<noamr> rossen: SebastianZ, with the prev resolution to move css-vt-1 to fairly stable, what else is remaining?
<Rossen_> q?
<noamr> SebastianZ: this was the most obvious 1 that was missing. anything else interoperable to add into the spec?
<noamr> ... I myself went through the specs and didn't find something in the status, but perhaps missed one
<noamr> rossen: I was going to put the q back to all of the group. are you working on any spec that can move to other state before we close the snapshot?
<noamr> ...: let's assume this is the only one. Chris Lilley was also didn't have opinions on this. didn't hear anything else
<noamr> RESOLVED: only change is the snapshot to record today is add css-view-transitions-1 to fairly stable
<noamr> rossen: going back, css anchor position? was already in the spec, Chris Lilley fixed
<noamr> RESOLVED: publish snapshot 2023 with css-view-transitions moving to fairly stable and css-scroll-snap moving to rough interoperability
<noamr> (sorry called it css-anchor-position earlier, meant css-scroll-snap)
<fantasai> RESOLVED: Republish snapshot 2022 as Group Note (not Draft Note)
<noamr> SebastianZ: not sure if this needs a resolution, but css 2022 is still published as group draft note
<dbaron> https://www.w3.org/TR/css-2022/
<noamr> thanks fantasai
<noamr> rossen: we have both resolution now, that's all on the issue
<noamr> SebastianZ: no other point
<noamr> rossen: let's jump into the view transitions topic
<fantasai> scribenick: fantasai

[svgeesus]

Should have been the other way round, i.e. it should be in the "Rough Interoperability" section

No, the order (from most complete to least complete) is:

2.1 Cascading Style Sheets (CSS) — The Official Definition
2.2 Fairly Stable Modules with limited implementation experience
2.3 Modules with Rough Interoperability

2.2 means "completed design work, and are fairly stable" while 2.3 means "their details are not fully worked out or sufficiently well-specified and they need more testing and bugfixing" i.e. not completed.

See for example

• [css-2021] CSS Counter Styles Level 3 is listed in 2.1 and 2.2 #6908

where a spec was moved up from 2.2 Fairly Stable to 2.1 Official (the issue being that it was copied not moved, so occurred in both places).

[svgeesus]

Publication requested 5 December, expected 7 December

[SebastianZ]

Probably a bit late now but I wonder whether Motion Path 1 should be added to "Rough Interoperability". It's still a WD, though it was covered by the Interop 2023 initiative and gained an interoperability of 99% (with Mozilla just having published their intent to ship the remaining parts of their implementation).

Sebastian

[svgeesus]

Certainly too late for this week's publication, but we could squeeze in another one this year if we get consensus to add it. If not, it would be CSS 2024 which I believe we should get started on early in 2024.

[astearns]

Let’s use this as the reason to start snapshot 2024

[svgeesus]

Let’s use this as the reason to start snapshot 2024

• Starting CSS 2024 #9681

[svgeesus]

Published today