| 1 | = Tasks = |
| 2 | |
| 3 | '''WebGL''' |
| 4 | |
| 5 | EGL context creation for offscreen rendering creates a pixmap or a pbuffer. Wayland-egl does not support pixmaps so we should try to use pbuffers in this case. |
| 6 | |
| 7 | '''Fullscreen video playback''' |
| 8 | |
| 9 | Fullscreen video involves the creation of a fullscreen window and a sink that can render to that window using the video overlay interface. Current waylandsink from gst-plugins-bad does not implement the video overlay interface though. As an alternative, we can try to do composited video also for fullscreen. |
| 10 | |
| 11 | '''Plugins''' |
| 12 | |
| 13 | The plugin process requires GTK2, which does not support Wayland. Plugins are not expected to be ported to GTK3 so this will be a problem. Maybe XWayland can help with this. |
| 14 | |
| 15 | '''Accelerated Compositing''' |
| 16 | |
| 17 | There are two parts to this problem: |
| 18 | |
| 19 | * Sharing a surface between the UI and Web processes. |
| 20 | * There is no surface sharing API in Wayland at the moment though so this is a problem that needs to be solved. An alternative could be to have one of the processes play the role of a wayland compositor so thet that both of them can share the surface (in the same way a regular weston client can share a buffer with the weston compositor). |
| 21 | * Paint the surface with GTK without having to download the surface to the main memory. |
| 22 | * Some of this work may require support in GTK/Cairo/Wayland. |
| 23 | |
| 24 | '''Layout Tests''' |
| 25 | |
| 26 | We need a way to run layout tests in Wayland. Current tests run with Xvfb, we should try to run them with Weston instead and see if Weston can run offscreen. |