- From: Xiaocheng Hu via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Aug 2023 22:21:05 +0000
- To: public-css-archive@w3.org
> I think the spec currently implies that they win over everything This is also my understanding of the spec, and what the Chromium implementation is doing. > ...which imho is not great. Agreed it's not great, but it would be very hard to change. The main difficulty is that we need to run layout to decide which fallback position to apply, at which time the cascade is already finished. That's why everything is done at used value time. It would be really great if we can resolve fallback postion at computed value time, which not only prevents overwriting e.g. `!important` UA style, but also supports [smooth transitions between fallback positions](https://github.com/w3c/csswg-drafts/issues/8372). -- GitHub Notification of comment by xiaochengh Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9149#issuecomment-1699929804 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 August 2023 22:21:07 UTC