[css-2023] Start on CSS Snapshot 2023

[SebastianZ]

We are in the fourth quarter of 2022, so I think we should slowly start talking about the changes necessary to finish up the CSS Snapshot 2022.

Regarding the stability levels, the current list doesn't differ much from the one at the end of last year.
There are three specs, though, which made a big leap forward, from (FP)WD to CR:

• CSS Color Adjustment Level 1
• CSS Conditional Rules Level 4
• CSS Cascading and Inheritance Level 5

The first one is already part of CSS 2022, the other two should probably be considered.

Also, many of the specs covered by the Interop 2022 project can probably be moved to the "Rough Interoperability" section. One of them is definitely CSS Scroll Snap 1, for example.

The goal of this issue is to summarize the things that need to be changed so that the CSS Snapshot 2022 can be published.

Sebastian

[svgeesus]

chris@SuperNomad:/mnt/c/Users/chris/Documents/GitHub/csswg-drafts/css-2022$ bikeshed -f spec
WARNING: Multiple elements have the same ID 'css'.
Deduping, but this ID may not be stable across revisions.
LINE ~363: Couldn't find target document section css:
[[#css|official definition of CSS]]
LINE ~451: Couldn't find target document section css:
[[#css|official definition of CSS]]
 ✔  Successfully generated, but fatal errors were suppressed

However I'm only finding one such id in the .bs, the other must be autogenerated:

<h3 id="css">Cascading Style Sheets (CSS) &mdash; The Official Definition</h3>

aha the other one is

1.1. What is CSS?

Cascading Style Sheets (CSS)

[SebastianZ]

@svgeesus What about the suggested additions above? Should we discuss them on the next call?

Sebastian

[svgeesus]

It's a bit late, publication is already underway and happened today

[astearns]

We resolved to update the snapshot as needed instead of publishing only once a year, so these changes could still be discussed and added for 2022. Or they could form the basis for an early 2023 update.

[svgeesus]

Of course. I meant that the First Note had already been published, not that we couldn't update it with a later publication.

[SebastianZ]

Fine, so I've set Agenda+ so we can talk about that. And yes, I saw that it got published and that any changes need to be discussed afterwards.

Sebastian

[astearns]

Unfortunately we have had higher-priority issues that have pushed this back. Let’s take this up as a 2023 update next month.