The delta-spec model has made adding features to css-view-transitions-2 a bit awkward and counterproductive.
See #9773 for example.
The more we advance the feature, the more this is likely to make that problem more difficult.

Suggesting instead to have a single level for CSS view-transitions, and keep things in an editor draft, moving to /TR/ once they're stable, but without levels. (Is that the model for css-syntax?)

We should still be careful about feature-detection, to make sure subfeatures are properly detected (e.g. you don't assume view-transition-class is supported just because view-transition-name is supported).

Alternate proposals for cleaner models also appreciated.

/cc @tabatkins @khushalsagar @vmpstr @nt1m