- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Jun 2023 21:59:45 +0000
- To: public-css-archive@w3.org
There's 2 types of UA style rules in this spec: 1. Static styles which are split across [User Agent Styles](https://drafts.csswg.org/css-view-transitions-1/#ua-styles) and [View Transition Pseudo Elements](https://drafts.csswg.org/css-view-transitions-1/#view-transition-pseudos). I don't have a strong preference between inlining the styles with the defining of each pseudo vs one section for all of them after the pseudos. How about moving the "User Agent styles" section after "Pseudo Elements" and adding all the static styles there? 2. Dynamic styles which are generated using layout info from each element and are Document scope. The stylesheet is defined [here](https://drafts.csswg.org/css-view-transitions-1/#document-view-transition-style-sheet) and the exact values are part of the algorithms which generate the styles. These should stay as-is since how the style values are generated is intertwined with these algorithms. > Probably at that point we should make sure they're upstreamed to HTML etc. I didn't follow this. The styles in this spec apply to all namespaces (not just html). This came up on https://github.com/w3c/csswg-drafts/issues/8573 with the conclusion that it makes sense for each CSS spec to define styles which apply to all namespaces. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8891#issuecomment-1574361526 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 June 2023 21:59:46 UTC