- From: Noam Rosenthal via GitHub <noreply@w3.org>
- Date: Wed, 03 Dec 2025 10:12:02 +0000
- To: public-css-archive@w3.org
> Yes I still share this concern.
It's valid to have concerns about footguns, but I still hold on to the arguments made in https://github.com/w3c/csswg-drafts/issues/13117#issuecomment-3547846978 that this is a net benefit also for performance.
> The proposal encourages including CSS on pages that does not need them.
It encourages keeping common styles together, with being enable to make per-route exceptions when those exists.
I'm in disagreement that having a separate `page1.css` and `page2.css` etc is a good performance practice for most cases and something that should be encouraged by the platform. See comment above.
> Given that he driver for the proposal is to have > special animations on transitions, limiting the conditional to only those types of animations makes the most sense to me.
There are other use cases though.
e.g. setting the initial scroll target in a swipe/tabs UI:
```css
@navigation(at: home) {
#home-tab { scroll-initial-target: nearest; }
}
```
This type of setup can potentially save a lot of messy broilerplate Javascript and be a performance net benefit.
--
GitHub Notification of comment by noamr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13117#issuecomment-3606067378 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 December 2025 10:12:04 UTC