- From: vmpstr <notifications@github.com>
- Date: Wed, 14 Aug 2024 11:00:45 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 14 August 2024 18:00:49 UTC
I think Noam covered most of our reasons here.
I'd just like to highlight that the `view-transition-name` and `view-transition-class` are somewhat analogous to `id` and `class` in html. However, because it's set in CSS it allows us to add this property easier in some situations without requiring attribute changes. For example,
```css
.container > div {
view-transition-class: container-item;
}
```
this isn't as ergonomic if you require that the `div`s within the container have a common `class` specified on them. It may be common that this is already the case, but coupling view transitions with existing classes seems more restrictive in general.
--
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/938#issuecomment-2289487640
You are receiving this because you are subscribed to this thread.
Message ID: <w3ctag/design-reviews/issues/938/2289487640@github.com>
Received on Wednesday, 14 August 2024 18:00:49 UTC