- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Dec 2023 17:13:53 +0000
- To: public-css-archive@w3.org
I'd want to bump this issue. Just today I had a bug at work where there was a significant difference between Safari and Chrome resulting in a significant visual difference between elements due to the absent interoperability of subpixel values. - I did mention this in Mastodon today: https://front-end.social/@kizu/111585513495742346 (after which I did find this issue). - I did found a post by @huijing who did bring this issue up in 2019: https://chenhuijing.com/blog/about-subpixel-rendering-in-browsers/ - In her post, she mentions a post by @jeresig from 2008: https://johnresig.com/blog/sub-pixel-problems-in-css/ Subpixel interop is something I constantly stumble upon in practice. Currently, we have to use preprocessors for rounding things. With `round()` we will be able to apply fixes more reliably, _but_ it won't change the status quo, where unless you'll explicitly opt in to using `round()` for _every_ place that requires it, things might look different and result in bugs. Having some way to control this on a scale will be great. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2127#issuecomment-1858215632 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 December 2023 17:13:55 UTC