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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Dec 8 21:41:28 PST 2016


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

Carlos Alberto Lopez Perez <clopez at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |clopez at igalia.com

--- Comment #13 from Carlos Alberto Lopez Perez <clopez at igalia.com> ---
(In reply to comment #11)
> (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.
> 

An idea is to build a black-list of hardware and drivers that we know are broken with WebKitGTK+.

At run-time we fetch the information about the hardware and drivers/versions of the machine, and by default we only enable AC if the combination is not blacklisted.

When a user reports a bug about rendering broken with WebKitGTK+, we can ask the information about the hardware and drivers/versions and we blacklist it. The blacklist entry should contain a link to a bug in this bugzilla where the bug itself would be eventually fixed (if it's an issue on WebKit itself rather than on the drivers). But in the meanwhile, at least we ensure that this problematic hardware/driver gets blacklisted ASAP, and that the user can use WebKitGTK+ without major issue on the hardware.


Chrome does this: they have an extensive list of hardware and drivers that should be avoided. [1] This is a good resource to start building this list.



[1] https://chromium.googlesource.com/chromium/deps/gpu/software_rendering_list/+/467471226a0453e9613db84879fa0dcabc149689/software_rendering_list.json

-- 
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/20161209/e71936b4/attachment-0001.html>


More information about the webkit-unassigned mailing list