[Webkit-unassigned] [Bug 165246] [GTK] Fails to draw in Wayland with enabled compositing mode

[bugzilla-daemon at webkit.org]

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

--- Comment #11 from Michael Catanzaro <mcatanzaro at igalia.com> ---
(In reply to comment #10)
> I guess you are talking only about wayland, right?

I think users are complaining with X11 as well. But yes, I'm primarily concerned with Wayland. The problem is that it works fine for you and me regardless, but a bunch of users (including many on IRC who don't report bugs) seem to have hardware-specific issues, and there's nothing we can do except shrug and say "maybe your graphics driver is broken" -- then everyone's dissatisfied as nobody knows what to do with such a bug. The most important problem is that no WebKit developer except you is looking at the bugs at all.

> I know some people also
> having problems under X11, but I haven't seen so many complains. I think the
> main issue in wayland is that we also use GL on the UI process side, and
> gdk_gl is probably not ready or mature enough yet. That's why I asked if
> that also happened when using glReadPixels.

Well we need to prepare some test patch or something, or we'll never get an answer to that question.

> We can always disable everything
> that doesn't work, but we can also try to fix and find alternative solutions
> in the meantime. For example, in this case if the problem is gdk_gl, let's
> try using glReadPixels always. Another idea would be to go back to
> enter/leave AC mode only when required. I agree it's a waste of time and
> memory having AC enable to show about:blank.

I don't think AC mode is actually required on any website that triggers it; in fact, my experience has historically been that websites that trigger it (reuters.com, github.com) render much faster and more reliably without it.

It occurs to me that there is one really big downside to disabling it, though, which is that we'll have to deal with bug #126122 once again. That's a major problem, so we're out of luck either way.

-- 
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/20161207/15b76638/attachment.html>