From Fedora Project Wiki

m
m
Line 17: Line 17:
 
== remote display ==
 
== remote display ==
  
protocol, mutter
+
<code>protocol, mutter</code>
  
 
== screencast ==
 
== screencast ==
  
mutter, apps
+
<code>mutter, apps</code>
  
 
== primary selection ==
 
== primary selection ==
  
protocol, gtk+, mutter, Xwayland
+
<code>protocol, gtk+, mutter, Xwayland</code>
  
 
https://wiki.gnome.org/Initiatives/Wayland/PrimarySelection
 
https://wiki.gnome.org/Initiatives/Wayland/PrimarySelection
Line 31: Line 31:
 
== input methods ==
 
== input methods ==
  
protocol, gtk+, mutter
+
<code>protocol, gtk+, mutter</code>
  
 
FIXME: I have no idea where we stand wrt input methods nor what is really meant by that.
 
FIXME: I have no idea where we stand wrt input methods nor what is really meant by that.
Line 38: Line 38:
 
== on-screen keyboard ==
 
== on-screen keyboard ==
  
protocol, mutter
+
<code>protocol, mutter</code>
  
 
{{admon/note|FIXME|Not sure if we'd need a new app for that.}}
 
{{admon/note|FIXME|Not sure if we'd need a new app for that.}}
Line 44: Line 44:
 
== relative/locking pointer confinement ==
 
== relative/locking pointer confinement ==
  
protocol, libraries
+
<code>protocol, libraries</code>
  
 
Required for games
 
Required for games
Line 54: Line 54:
 
== hi-dpi support ==
 
== hi-dpi support ==
  
protocol, gtk+, mutter
+
<code>protocol, gtk+, mutter</code>
  
 
{{admon/note|FIXME|Not sure what is meant by that, Wayland supports scaling of surfaces and mutter uses that afaik.}}
 
{{admon/note|FIXME|Not sure what is meant by that, Wayland supports scaling of surfaces and mutter uses that afaik.}}
Line 60: Line 60:
 
== attached modal dialogs ==
 
== attached modal dialogs ==
  
gtk+, mutter
+
<code>gtk+, mutter</code>
  
 
This should use the existing "set_parent" request in xdg-shell protocol.
 
This should use the existing "set_parent" request in xdg-shell protocol.
Line 66: Line 66:
 
== tablet support ==
 
== tablet support ==
  
protocol, libraries, gtk+
+
<code>protocol, libraries, gtk+</code>
  
 
== startup notification ==
 
== startup notification ==
  
protocol, libraries, gtk+, mutter
+
<code>protocol, libraries, gtk+, mutter</code>
  
 
== clipboard proxy for xwayland ==
 
== clipboard proxy for xwayland ==
  
Xwayland
+
<code>Xwayland</code>
  
 
{{admon/note|FIXME|Not sure what is meant by that, copy/paste already works between Wayland native and Xwayland apps.}}
 
{{admon/note|FIXME|Not sure what is meant by that, copy/paste already works between Wayland native and Xwayland apps.}}
Line 80: Line 80:
 
== touch proxy for xwayland ==
 
== touch proxy for xwayland ==
  
protocol, gtk+, mutter, Xwayland
+
<code>protocol, gtk+, mutter, Xwayland</code>
  
 
{{admon/note|FIXME|Not sure what is meant by that, touch was added in Wayland and Xwayland by Carlos.}}
 
{{admon/note|FIXME|Not sure what is meant by that, touch was added in Wayland and Xwayland by Carlos.}}
Line 86: Line 86:
 
== accessibility features ==
 
== accessibility features ==
  
protocol, gtk+, mutter
+
<code>protocol, gtk+, mutter</code>
  
 
== output rotation ==
 
== output rotation ==
  
mutter, apps
+
<code>mutter, apps</code>
  
 
Wayland protocol already supports output transformation, supported by Xwayland and weston can use it.
 
Wayland protocol already supports output transformation, supported by Xwayland and weston can use it.
Line 96: Line 96:
 
== XRandR control of Wayland outputs ==
 
== XRandR control of Wayland outputs ==
  
protocol, Xwayland
+
<code>protocol, Xwayland</code>
  
 
There is a "read-only" XRandR support in Xwayland, but it cannot send request back to the Wayland compoisitor so X11 applications have no control over the output configurations.
 
There is a "read-only" XRandR support in Xwayland, but it cannot send request back to the Wayland compoisitor so X11 applications have no control over the output configurations.
Line 102: Line 102:
 
== screensaver control ==
 
== screensaver control ==
  
protocol, mutter, Xwayland, apps
+
<code>protocol, mutter, Xwayland, apps</code>
  
 
https://bugs.freedesktop.org/show_bug.cgi?id=89440
 
https://bugs.freedesktop.org/show_bug.cgi?id=89440
Line 110: Line 110:
 
== Xfree86-VidModeExtension in Xwayland ==
 
== Xfree86-VidModeExtension in Xwayland ==
  
protocol, Xwayland
+
<code>protocol, Xwayland</code>
  
 
Some games check for this extension and would refuse to start without.
 
Some games check for this extension and would refuse to start without.

Revision as of 14:59, 19 November 2015

Wayland Desktop features progress

This purpose of this page is to list the current missing or incomplete features in GNOME on Wayland to achieve a user experience on par with what is found on X11.

This page is not meant to list known bugs or issues with existing features, nor how to debug Wayland issues, see How to debug Wayland problems for this.

It focuses primarily on GNOME because GNOME is the default desktop on Fedora Workstation, but features may need to be implemented at different levels not necessarily part of GNOME:

* kernel: drm, evdev, etc.
* libraries: underlying libraries, e.g. libinput, libwayland, etc.
* protocol: requires a new Wayland protocol or amending an existing protocol
* Xwayland: X11 compatibility
* mutter: Wayland compositor
* gtk+: toolkit, handles client side decorations in Wayland
* apps: requires new applications

remote display

protocol, mutter

screencast

mutter, apps

primary selection

protocol, gtk+, mutter, Xwayland

https://wiki.gnome.org/Initiatives/Wayland/PrimarySelection

input methods

protocol, gtk+, mutter

FIXME: I have no idea where we stand wrt input methods nor what is really meant by that.

Note.png
FIXME
I have no idea where we stand wrt input methods nor what is really meant by that

on-screen keyboard

protocol, mutter

Note.png
FIXME
Not sure if we'd need a new app for that.

relative/locking pointer confinement

protocol, libraries

Required for games

http://lists.freedesktop.org/archives/wayland-devel/2014-December/018653.html

http://lists.freedesktop.org/archives/wayland-devel/2015-October/024726.html

hi-dpi support

protocol, gtk+, mutter

Note.png
FIXME
Not sure what is meant by that, Wayland supports scaling of surfaces and mutter uses that afaik.

attached modal dialogs

gtk+, mutter

This should use the existing "set_parent" request in xdg-shell protocol.

tablet support

protocol, libraries, gtk+

startup notification

protocol, libraries, gtk+, mutter

clipboard proxy for xwayland

Xwayland

Note.png
FIXME
Not sure what is meant by that, copy/paste already works between Wayland native and Xwayland apps.

touch proxy for xwayland

protocol, gtk+, mutter, Xwayland

Note.png
FIXME
Not sure what is meant by that, touch was added in Wayland and Xwayland by Carlos.

accessibility features

protocol, gtk+, mutter

output rotation

mutter, apps

Wayland protocol already supports output transformation, supported by Xwayland and weston can use it.

XRandR control of Wayland outputs

protocol, Xwayland

There is a "read-only" XRandR support in Xwayland, but it cannot send request back to the Wayland compoisitor so X11 applications have no control over the output configurations.

screensaver control

protocol, mutter, Xwayland, apps

https://bugs.freedesktop.org/show_bug.cgi?id=89440

http://lists.freedesktop.org/archives/wayland-devel/2015-November/025582.html

Xfree86-VidModeExtension in Xwayland

protocol, Xwayland

Some games check for this extension and would refuse to start without. There are patches contributed but these are incomplete and not satisfactory.

Beside, this is the same a current XRandR support, i.e. read-only, Xwayland apps cannot control the output configuration.

https://bugs.freedesktop.org/show_bug.cgi?id=87806 http://lists.x.org/archives/xorg-devel/2015-September/047460.html http://lists.x.org/archives/xorg-devel/2015-October/047559.html