- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jan 2025 21:16:25 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-pseudo] `color-scheme` should be an allowed property for highlight pseudos``, and agreed to the following: * `RESOLVED: Add forced-color-adjust and color-scheme to set of properties that work with highlight pseudo, taking value from originating element` <details><summary>The full IRC log of that discussion</summary> <kbabbitt> fantasai: for highlight pseudos we have 2 wasy of applying properties<br> <kbabbitt> ...<br> <bramus> list of props: https://drafts.csswg.org/css-pseudo-4/#highlight-styling<br> <kbabbitt> ... props specified on highlight pseudo element eg. color, ...<br> <kbabbitt> ... and props we take from the originating element<br> <kbabbitt> ....e..g font properties<br> <kbabbitt> ... for this issue, we should decide are we taking this value directly off highlight pseudo?<br> <kbabbitt> ... in which case it inherits through pseudo's ancestry<br> <kbabbitt> ... or are we taking from originating element<br> <kbabbitt> ... for forced-color adjust and color scheme I think we want from originating element<br> <bramus> +1<br> <kbabbitt> ... then that will match unterlying element<br> <dbaron> +1<br> <kbabbitt> astearns: in my read of stephen's comment he would agree<br> <kbabbitt> schenney: yes I agree<br> <kbabbitt> fantasai: forced-color-adjust should behave same as color-scheme<br> <kbabbitt> Proposed: Add forced-color-adjust and color-scheme to set of properties that work with highlight pseudo, taking value from originating element<br> <kbabbitt> bramus: forced is already on that list<br> <lea> +1<br> <kbabbitt> astearns: objections?<br> <kbabbitt> bramus: color-scheme is already listed<br> <lea> I don't see why we may NOT want to allow these<br> <kbabbitt> RESOLVED: Add forced-color-adjust and color-scheme to set of properties that work with highlight pseudo, taking value from originating element<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11011#issuecomment-2622870741 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 January 2025 21:16:26 UTC