Open izuzak opened 3 months ago
This is likely an issue with the color space/management set by the individual system rather than a loss of precision. The ideal solution would be to encode everything in a Linear color space and convert it to the system color space on render.
Not to mention that most color spaces are based on numerical rather than perceptual properties, so there is a lot of variation between devices. Adopting a perceptual color space like OK Lab would help maintain perceived color across implementations.
Check for existing issues
Describe the bug / provide steps to reproduce it
I'm working on a theme and setting the
syntax.property.color
value to#2C78BF
. And I see the color of those UI elements change, but the color is slightly different as reported by the color picker -- it says the color is#2D78BF
. See first screenshot.I don't notice this for every color, though -- the color for
syntax.string.color
is#98BC37
and the color picker reports exactly that value. See second screenshot.The behavior doesn't seem to be related to which UI/syntax property the color is associated with, but with the color itself. E.g. if I set
syntax.string.color
to#2C78BF
, then it still comes out "wrong" as#2D78BF
.I mentioned this in the Zed discord channel and @maxdeviant said:
Environment
Zed: v0.126.0 (Zed Preview) OS: macOS 14.3.1 Memory: 64 GiB Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
Screenshot 1:
Screenshot 2:
If applicable, attach your
~/Library/Logs/Zed/Zed.log
file to this issue.No response