-
-
Save pandasauce/398c080f9054f05bee6e1c465416b53b to your computer and use it in GitHub Desktop.
| # 75.0.3770.142 | |
| 0x04b58615 7626 => 9090 0x04b58615 | |
| 0x04b5861d 31c0488945 => 9090909090 0x04b5861d | |
| Due to a beautiful bug in Chromium, it turns out you don't need this binary patch and can **enable** subpixel positioning by asking Chrome **to disable it**: https://bugs.chromium.org/p/chromium/issues/detail?id=824153#c39 | |
| Needless to say, I won't be maintaining this gist any longer. |
Due to a beautiful bug in Chromium, it turns out you don't need this binary patch and can enable subpixel positioning by asking Chrome to disable it: https://bugs.chromium.org/p/chromium/issues/detail?id=824153#c39
Needless to say, I won't be maintaining this gist any longer.
User need to re-compile though, right? Is there any flag ?
@AnwarShah, no. Just add --disable-font-subpixel-positioning as a command line argument when launching Chrome. It will do the exact opposite to what it says and enable subpixel positioning unconditionally.
@pandasauce That's awesome actually. I'm immediately seeing much improvement on brave browser which is chromium based. The texts are much sharper. Thanks!
Glad you like it. Something that is implied, but maybe I should point it out: this trick applies to all Chromium-based desktop applications too, i.e. Spotify and Slack.
Yeah. I knew it.
Due to a beautiful bug in Chromium, it turns out you don't need this binary patch and can enable subpixel positioning by asking Chrome to disable it: https://bugs.chromium.org/p/chromium/issues/detail?id=824153#c39
Needless to say, I won't be maintaining this gist any longer.