Wayland issues on HiDPI

[evan-a-a]

After the series of commits enabling Wayland by default (https://github.com/flathub/com.slack.Slack/commit/88b64d7d09812ca9b784b4ae07a11d31c4427fa5, https://github.com/flathub/com.slack.Slack/commit/a172f34d4691f64848e5f3a5d39250660a3e8b8c, https://github.com/flathub/com.slack.Slack/commit/a8ceac4d3121109adfe9344568b95e523db1c09b), there are a number of issues with HiDPI displays, and possibly in other configurations. These issues are present in some Chromium and Chromium based browsers as well, and are a sign of the lack of maturity in the Chromium wayland backend. In no particular order:

• Wayland window decorations are missing the close button
• HiDPI with scaling results in a blurred interface
• Cursor is chopped in half and missing the bottom portion (not shown)

Until Chromium's wayland maturity has improved, I would recommend reverting the optimistic use of Wayland by default. Notably, other Chroium based flatpaks (Edge, Chrome, Brave) haven't migrated to Wayland by default yet due to these issues.

[David-VTUK]

Temporary workaround for anyone who has come across this:

Use Flatseal to disable the Wayland window system:

Which restores the window decorations and removes general UI blurriness:

When Wayland is enabled:

[benwaffle]

These happen on a LoDPI screen:

• Wayland window decorations are missing the close button
• Cursor theme looks different from normal

[sisou]

Additionally for me, on a regular DPI screen (14" FullHD), with the now-default wayland settings, when in fullscreen, there's a transparent gap between the app and the edge of the screen (while the title bar without controls is full-width). This does not happen when windowed.

Fullscreen:

Windowed:

The workaround to disable Wayland via Flatseal works for me, thanks @David-VTUK!