Announcement
Collapse
No announcement yet.
The Wayland Issues Still Ahead Of Fedora 24
Collapse
X
-
That list is surprisingly small... on-screen keyboard just needs to figure out how to interface uinput with libinput (easy to do on console and interfacing with evdev for X) was a stackexchange question about this here http://stackoverflow.com/questions/3...-with-libinput (unanswered though...)
Tablet support well.. that's what I'd like to say too! I think Libinput already mostly supports tablets (both for drawing and those handheld thing'majugs) but the biggest problem is that there is no configuration front-end available for the supported devices (unless you are on X) btw I have found out that input drivers can to an extent work through xorg-wayland, according to xdotool anyways (which does) which could potentially be used to temporarily bypass this issue. The problem with it is that it cannot use some wayland native shortcuts (like alt+f4) which invoke wayland commands.
Positioning chooser... I don't know what that even means... but sounds easy.
I guess the biggest issue is accessibilty features, but looks like most of them are completed, or halfway there. (Let's forget about that XRandR thing, that is a BAD idea)
- Likes 1
Comment
-
Originally posted by Griffin View Post
Minor yes. Still it is important to do the considerations to quality and keep things testable. Fedora and Gnome have quality standards you know... If you want untested and untestable code thrown against the wall you need to look for other desktops.
Comment
-
-
I feel like some people don't understand that this is a blocker for making it default, i.e. applicable to everyone. I mean seriously, you can still choose wayland manually once in GDM and it will remember to always open wayland for you... it's been this way for a while.
Comment
Comment