- From: fantasai via GitHub <noreply@w3.org>
- Date: Wed, 25 Jun 2025 03:37:26 +0000
- To: public-css-archive@w3.org
CSS View Transitions Level 1 is in CR already, which generally implies that its feature set is frozen but that it continues to accept bugfixes. If there's something in particular in L2 we want to backport to L1 (e.g. `view-transition-class`), let's discuss that and do that now. Merging the L1 text up into Level 2 can be either editor's discretion or by WG resolution. I'm happy to support the action either way. I recommend, before merging the text, that outstanding edits against L1 be resolved and the draft republished, so that the text merged into L2 corresponds exactly to a snapshotted publication of L1. And then publish the resulting update of L2 so that there's a pair of publications that correspond. This will help you keep things in sync going forward, because it's a known good synchronization point. :) From that point forward, you'll want to try to keep edits to L1 features synchronized into both drafts. The bin/xcommit.pl script in the drafts repository can help you with this. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11202#issuecomment-3002843848 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 June 2025 03:37:27 UTC