- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Jan 2024 21:47:33 +0000
- To: public-css-archive@w3.org
Another example of awkwardness in the spec is [process old state captured](https://drafts.csswg.org/css-view-transitions-1/#viewtransition-process-old-state-captured). It's a callback used to inject code for cross-document transitions (which is the L2 spec) in the middle of an algorithm defined by the L1 spec. I've seen a lot of value in having an ED to incubate a new feature. It helps in iterating as we work through all the issues associated with a feature. The awkwardness is also reasonable in the interim state. But if we have to actually take L2 through the standards track, it becomes messy. So I'd prefer if we can use the ED to incubate but move features to a living spec once all associated issues have been resolved. Drawing from the html spec as an example (which is a living spec), IIRC the navigation API started off in a rough ED like spec and was then moved to the html spec in 1 PR? @domenic on that. Also @astearns @atanassov in case there's other CSS specs we can learn from. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9850#issuecomment-1908969355 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 January 2024 21:47:36 UTC