- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Nov 2023 15:26:17 +0000
- To: public-css-archive@w3.org
Keeping #9542 in mind, I think that (1) still makes the most sense to me, and also it's the simplest in the sense that types don't transfer across documents. Yes, types apply to the transition, but who said that they need to stay the same throughout the whole transition? They apply to the transition *at a given moment*. This would also be a solution for #9424 - in MPA we'd have different types in the two documents, and ichanging `viewTransition.typeList` in JS would be the equivalent. The problem that I have with anything that takes the old document into account (which is 2-5) in the new document is that it's unnecessarily opinionated about what types mean. Why not let the authors do that themselves? if they want to apply any kind of restrictions they can do it themselves based on their content rather than mandating this in the platform. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9526#issuecomment-1812744680 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 November 2023 15:26:19 UTC