-
Notifications
You must be signed in to change notification settings - Fork 642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[css-view-transitions-1] Consider centralizing UA style rules #8891
Comments
I agree. Related, I wonder if the snapshot should aggregate all the UA additions for the Official Definition specifications, for the same reason. |
@svgeesus Probably at that point we should make sure they're upstreamed to HTML etc. |
There's 2 types of UA style rules in this spec:
I didn't follow this. The styles in this spec apply to all namespaces (not just html). This came up on #8573 with the conclusion that it makes sense for each CSS spec to define styles which apply to all namespaces. |
@khushalsagar I think I agree that the generated styles need to stay where they are, it seems that consolidating the global sheet (and noting at the end that there is a generated sheet as well) would be a good idea.
I was referring to the HTML-specific styles. :) A lot of the UA rules we have in the CSS specs are currently just informative suggestions for HTML. The rules that apply to all namespaces (like those in View Transitions) should of course stay defined in CSS. |
The View Transitions spec has a lot of additions to the UA style sheet split across many sections. It's just a suggestion, but I wonder if it might be easier if these rules were all centralized into one section (after the definitions of all of the pseudo-elements so that we know what we're styling and how they relate).
The text was updated successfully, but these errors were encountered: