<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [GTK] Apps Using Webkit Under Wayland Do Not Render Pages (GNOME 3.15)"
href="https://bugs.webkit.org/show_bug.cgi?id=142334">bug 142334</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [GTK] Apps Using Webkit Under Wayland Do Not Render Pages (GNOME 3.15)"
href="https://bugs.webkit.org/show_bug.cgi?id=142334#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [GTK] Apps Using Webkit Under Wayland Do Not Render Pages (GNOME 3.15)"
href="https://bugs.webkit.org/show_bug.cgi?id=142334">bug 142334</a>
from <span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=142334#c4">comment #4</a>)
<span class="quote">> 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.</span >
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 <a href="show_bug.cgi?id=142334#c5">comment #5</a>)
<span class="quote">> gtk-3.16.4 webkit-2.8.3 epiphany-3.16.1 mesa-10-6.0</span >
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>