-
Notifications
You must be signed in to change notification settings - Fork 718
[css-pseudo] color-scheme
should be an allowed property for highlight pseudos
#11011
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
Comments
This seems like an oversight. |
Yes, I agree. I see no problem implementing this in Chromium. Async resolution is fine by me. |
The CSSWG will automatically accept this resolution one week from now if no objections are raised here. Anyone can add an emoji to this comment to express support. If you do not support this resolution, please add a new comment. Proposed Resolution: Add |
OK, changed my mind. :) We actually have two lists of properties involved here after resolving #7591 so we need to confirm which one we should be adding it to: the list of applicable properties, or the list of properties we steal from the originating element in order to resolve the applicable properties. Also, we should resolve Moving to the regular agenda. |
Thinking much more deeply about it ...
The key question then is whether there is a use case in which you want different Does anyone have a use case for |
The CSS Working Group just discussed
The full IRC log of that discussion<kbabbitt> fantasai: for highlight pseudos we have 2 wasy of applying properties<kbabbitt> ... <bramus> list of props: https://drafts.csswg.org/css-pseudo-4/#highlight-styling <kbabbitt> ... props specified on highlight pseudo element eg. color, ... <kbabbitt> ... and props we take from the originating element <kbabbitt> ....e..g font properties <kbabbitt> ... for this issue, we should decide are we taking this value directly off highlight pseudo? <kbabbitt> ... in which case it inherits through pseudo's ancestry <kbabbitt> ... or are we taking from originating element <kbabbitt> ... for forced-color adjust and color scheme I think we want from originating element <bramus> +1 <kbabbitt> ... then that will match unterlying element <dbaron> +1 <kbabbitt> astearns: in my read of stephen's comment he would agree <kbabbitt> schenney: yes I agree <kbabbitt> fantasai: forced-color-adjust should behave same as color-scheme <kbabbitt> Proposed: Add forced-color-adjust and color-scheme to set of properties that work with highlight pseudo, taking value from originating element <kbabbitt> bramus: forced is already on that list <lea> +1 <kbabbitt> astearns: objections? <kbabbitt> bramus: color-scheme is already listed <lea> I don't see why we may NOT want to allow these <kbabbitt> RESOLVED: Add forced-color-adjust and color-scheme to set of properties that work with highlight pseudo, taking value from originating element |
Issue w3c#11011 was resolved to take forced-colors and color-scheme from the originating element. Remove the note for the issue.
Issue #11011 was resolved to take forced-colors and color-scheme from the originating element. Remove the note for the issue.
The fact that the
color-scheme
CSS property is not allowed on highlight pseudo-elements (e.g.::selection
) has the side effect that thelight-dark()
function effectively cannot be used to style highlight pseudos (it will always consider the "light" value). I think it would make sense to just addcolor-scheme
to the list of allowed properties, which would make this possible.The text was updated successfully, but these errors were encountered: