Re: [csswg-drafts] [css-navigation] Concerns about `at` navigation rules creating CSS bloat (#13117)

> 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.

I might have misunderstood your argument here, from the other thread it sounded like you are saying that you shouldn't do it because then you would have duplicate styles between `page1.css` and `page2.css` but that is not how anyone does it. In the example I provided I showed there being a `shared.css` which contains the shared CSS between the pages.

-- 
GitHub Notification of comment by matthewp
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13117#issuecomment-3606826390 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 13:20:12 UTC