- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Nov 2023 10:42:17 +0000
- To: public-css-archive@w3.org
I think the core of the terminology overload/confusing here and in other places is that some of the terms in the `view-transition` namespace apply to the whole transition (`startViewTransition`, `type`, `::view-transition`, `:active-view-transition`, `@view-transition`) and some apply only to a participating element (`view-transition-name`, `view-transition-class`, `::view-transition-group`, `::view-transition-image-pair`, `::view-transition-old`, `::view-transition-new`). When I look at these two categories separately they perhaps make more sense. Not sure if there's a way to mitigate that as this existed before types/classes, perhaps when documenting them using this category separation. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8319#issuecomment-1829555486 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 November 2023 10:42:18 UTC