3 ms·

I'm surprised about the comment on sway, because afaik the issue mentioned about a blurry chrome was fixed a while ago[0]. Maybe it's caused by something else..

I'm surprised about the comment on sway, because afaik the issue mentioned about a blurry chrome was fixed a while ago[0]. Maybe it's caused by something else... [0] https://github.com/swaywm/sway/issues/1481#issuecomment-640441017 https://github.com/swaywm/sway/issues/1481#issuecomment-6404...

danshick 6y ago
It depends a ton on what distro you are using. Some distros that now ship with wayland native desktops have tons of downstream patching to smooth out the experience. If you run Arch for instance, the default Chromium package is not ozone, and will run with XWayland (although chromium-ozone is available in the AUR). It's possible your distro is doing something differently.
- mijoharas 6y ago
  I run arch, and the google-chrome-stable package appears to have sorted out it's hdpi scaling issues. I could be wrong though, a while back I did a lot of tweaks to beat the concept of hdpi and variable screen resolutions into my computer, so I don't exactly have a "clean" setup, and it could be something else, but the fonts look crisp on both the low res and high res screens. I can't say whether this is anything to do with whether it's a build with/without ozone, but it appears to work now (sorry don't know much more than that!)
  - mijoharas 6y ago
    I'd just like to correct my post above, it seems that chrome was running under XWayland, I think I'd just found an incantation of settings that made it look alright on both my high res/low res screens.
    - danshick 6y ago
      There is an xwayland[0] patch out there to fix this properly. Could it be that you're using something like this[1]? [0] https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/111 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests... [1] https://aur.archlinux.org/packages/sway-hidpi-git/ https://aur.archlinux.org/packages/sway-hidpi-git/

danshick 6y ago

It depends a ton on what distro you are using. Some distros that now ship with wayland native desktops have tons of downstream patching to smooth out the experience. If you run Arch for instance, the default Chromium package is not ozone, and will run with XWayland (although chromium-ozone is available in the AUR). It's possible your distro is doing something differently.

mijoharas 6y ago
I run arch, and the google-chrome-stable package appears to have sorted out it's hdpi scaling issues. I could be wrong though, a while back I did a lot of tweaks to beat the concept of hdpi and variable screen resolutions into my computer, so I don't exactly have a "clean" setup, and it could be something else, but the fonts look crisp on both the low res and high res screens. I can't say whether this is anything to do with whether it's a build with/without ozone, but it appears to work now (sorry don't know much more than that!)
- mijoharas 6y ago
  I'd just like to correct my post above, it seems that chrome was running under XWayland, I think I'd just found an incantation of settings that made it look alright on both my high res/low res screens.
  - danshick 6y ago
    There is an xwayland[0] patch out there to fix this properly. Could it be that you're using something like this[1]? [0] https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/111 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests... [1] https://aur.archlinux.org/packages/sway-hidpi-git/ https://aur.archlinux.org/packages/sway-hidpi-git/