[Webkit-unassigned] [Bug 142334] [GTK] Apps Using Webkit Under Wayland Do Not Render Pages (GNOME 3.15)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=142334

Michael Catanzaro <mcatanzaro at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Michael Catanzaro <mcatanzaro at igalia.com> ---
(In reply to comment #4) 
> As far as I've looked into this, the issue is that even under Wayland
> WebKitGTK+ is entering accelerated compositing mode, for which there's no
> support for just yet. This results in content not being displayed at all.

I tested this again today. When built without ENABLE_WAYLAND_TARGET, pages that trigger accelerated compositing do not load at all when running under XWayland -- that is just totally broken. But when built with ENABLE_WAYLAND_TARGET, accelerated compositing is not used and the pages work fine. So once 2.10 is out, distros can finally set ENABLE_WAYLAND_TARGET without having to disable ENABLE_X11_TARGET, thanks to Carlos Lopez, and we will be good. That was a very major problem and I'm glad it appears to be solved.

I think we can simply say that accelerated compositing is not supported without ENABLE_WAYLAND_TARGET, so I will say RESOLVED FIXED. Although if it's possible to detect that we're running under XWayland and disable accelerated compositing in that case, that would be even better.

(In reply to comment #5)
> gtk-3.16.4   webkit-2.8.3  epiphany-3.16.1 mesa-10-6.0

To be clear: if you upgrade to unstable WebKitGTK+ 2.9.3 and pass -DENABLE_WAYLAND_TARGET=ON to CMake, then this should work. Once the stable release 2.10.0 is out, please ask the Arch folks to use ENABLE_WAYLAND_TARGET to update and use ENABLE_WAYLAND_TARGET, then this should work.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150701/c41854bf/attachment.html>