- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Oct 2018 12:25:23 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `scrollbar styling`, and agreed to the following: * `RESOLVED: getComputedStyle() resolves colors same as other color properties, but other keyword values return as the keywrd` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: scrollbar styling<br> <fantasai> tantek: We did FPWD already<br> <fantasai> https://www.w3.org/TR/css-scrollbars-1/<br> <fantasai> heycam: Not sure who put this on the agenda, but I can make a demo if ppl want<br> <fantasai> tantek: we have an implementation in nightly<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/3237<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/3237<br> <fantasai> heycam: Question about what should happen with getComputedStyle() and the scrollbar color<br> <fantasai> heycam: Not sure we want to use resolved value<br> <fantasai> heycam: strange to have auto value become something else<br> <fantasai> heycam: would like to use the actual comptued value<br> <fantasai> dbaron: Is there a distinction between "auto or comptued color" and auto and used color?<br> <fantasai> emilio: We resolve computed color<br> <fantasai> heycam: I don't think we should resolve auto to a color<br> <fantasai> tantek: Also this is two colors, not just one<br> <fantasai> tantek: We had two properties, folded to one<br> <fantasai> tantek: Can also say if you want dark or light theme scrollbar colors<br> <fantasai> tantek: so not just a color property, a bit more complicated<br> <fantasai> fantasai: so if you specify a non-<color> keyword, return that keyword, otherwise return the same kind of resolved color as other color properties<br> <tantek> resolved colors (plural)<br> <fantasai> RESOLVED: getComputedStyle() resolves colors same as other color properties, but other keyword values return as the keywrd<br> <fantasai> heycam demos Firefo's implementation<br> <gregwhitworth> very, very cool heycam<br> <fantasai> tantek: Based on this implementation experience, we're pretty happy for light and dark for colors, and being able to specify colors<br> <fantasai> tantek: dark is interesting for web apps that have a dark theming regardless of what the OS theme is<br> <fantasai> tantek: Regarding width, having just thin vs not has been suficient for the use cases we've needed<br> <fantasai> tantek: we haven't implemented the <length> value and would be OK with dropping that<br> <fantasai> tantek: don't know if there are other implementers that have thought about this since Syndye<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3237#issuecomment-432224775 using your GitHub account
Received on Tuesday, 23 October 2018 12:25:24 UTC