New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native Wayland support #18
Conversation
Started test build 113262 |
Build 113262 successful
|
Started test build 113276 |
Build 113276 successful
|
Started test build 113277 |
Build 113277 successful
|
Needs further testoing
Started test build 113286 |
Build 113286 successful
|
Yes, that's what I wanted to do - to simulate a fresh install.
The result is the same:
After the first start I can enable wayland and it works fine. So I guess we should wait for an upstream electron bump before we enable this. |
To me as long as it is not the default in the platform it shouldn't be merged. |
And by platform, here I mean Electron. |
The primary reason I prefer native Wayland is that scaling doesn't work correctly with XWayland and therefore XWayland applications are blurry on HiDPI-screens. But I'm fine with enabling Wayland locally for me. |
This makes sense. As the advice for electron apps on flathub's documentation is not to enable wayland. @sebastian-de i understand that xWayland is not perfect but after hearing what @hfiguiere said until those two requirements are met i agree with them on NOT merging this and if you truly want wayland native then you would be better patching this in yourself. If things change in the future then we can look at this again but until then i'm going to close this pr and pin it for future reference. |
Tested on KDE Plasma Wayland/X11 with amdgpu
--ozone-platform-hint=auto
should be enough once electron/electron#34937 finds its way into the Electron version used by Arduino IDE.Thanks for creating this flatpak!