We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 5331 - Suggestion: default to Wayland for better compatibility, at least on mobile (or maybe everywhere?)
Summary: Suggestion: default to Wayland for better compatibility, at least on mobile (...
Status: ASSIGNED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.12
Hardware: All Linux
: P2 enhancement
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on: 5194
Blocks:
  Show dependency tree / graph
 
Reported: 2020-10-27 23:09 UTC by Ellie
Modified: 2021-01-29 09:11 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ellie 2020-10-27 23:09:13 UTC 
On the PinePhone, it appears SDL2 defaults to XWayland still. This means issues with scaling and such, because the X11 compatibility of the new phone-centric mobile desktops is often quite basic and incomplete. I would anticipate this to possibly remain that way since GTK+ and Qt work nicely with Wayland, so there is no incentive for those new desktops to iron out the X11 support for all corner cases. As a result, SDL2 defaulting to X11/XWayland (without an env var set to change this) means it automatically runs in a buggier second class mode.

Would it therefore make sense to always have SDL2 try Wayland first? I can't really see the harm in an X11-only environment, where that would simply fail and then SDL2 would fall back to X11 anyway. Or am I missing something? Is there a reason this isn't how it currently operates other than nobody thought of it so far?