3 ms·

Current status: still sucks, unfortunately. From what I've seen the developers have more-or-less decided that it would be a lot of effort to get scaling and inp

Current status: still sucks, unfortunately. From what I've seen the developers have more-or-less decided that it would be a lot of effort to get scaling and input to work correctly for X applications with HiDPI, and they'd rather work on new things, not supporting old things. Which I certainly understand, but it kills the experience for most applications that I tend to use. So I can't really switch until that changes or more applications support wayland natively.

e12e 8y ago
Is this only a problem with x11 apps? If so, I'm a little surprised there's not a Wayland based build for Electron that'd make it easy to fix the issue for vscode? Hm, looks like the branch/subproject in chrome is "ozone" and some work is ongoing there: https://github.com/electron/electron/issues/9056 https://github.com/electron/electron/issues/9056 https://github.com/Igalia/chromium/tree/ozone-wayland-dev https://github.com/Igalia/chromium/tree/ozone-wayland-dev