Bug 193972 - [GTK] Temporarily switch default hardware acceleration policy to WEBKIT_HARDWARE_ACCELERATION_POLICY_NEVER
Summary: [GTK] Temporarily switch default hardware acceleration policy to WEBKIT_HARDW...
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 192523
  Show dependency tree / graph
 
Reported: 2019-01-29 11:52 PST by Michael Catanzaro
Modified: 2019-01-30 09:54 PST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Catanzaro 2019-01-29 11:52:16 PST 
In bug #192523 we are tracking a few issues with accelerated compositing mode. In particular, I consider bug #192522 a blocker for 2.24. It's not a regression in WebKit, but somewhere else in the graphics stack, but it will probably soon be visible to users so we'll have to deal with it now.

Of course I don't know how to fix these issues, and I don't think we should release in this state, and we've reached the end of the release cycle, so I'm left with unhappily suggesting that we switch the default WebKitHardwareAccelerationPolicy to WEBKIT_HARDWARE_ACCELERATION_POLICY_NEVER, at least temporarily. If graphics developers have other suggestions, I'm all ears, but bug #192522 is very severe.

Problems this will cause:

 * 3D transforms will be broken
 * Performance on tablets and phones will be tanked; these are important targets for GTK port
Comment 1 Michael Catanzaro 2019-01-30 07:18:50 PST 
I wonder if this has been fixed in bug #193903. I will investigate that first.
Comment 2 Michael Catanzaro 2019-01-30 09:54:45 PST 
Carlos Garcia doesn't want to do this. Closing.