193972 2019-01-29 11:52:16 -0800 [GTK] Temporarily switch default hardware acceleration policy to WEBKIT_HARDWARE_ACCELERATION_POLICY_NEVER 2019-01-30 09:54:45 -0800 1 1 1 Unclassified WebKit WebKitGTK WebKit Nightly Build PC Linux RESOLVED WONTFIX P2 Normal --- 192523 1 mcatanzaro webkit-unassigned bugs-noreply magomez mcatanzaro zan oldest_to_newest 1499628 0 mcatanzaro 2019-01-29 11:52:16 -0800 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 1499996 1 mcatanzaro 2019-01-30 07:18:50 -0800 I wonder if this has been fixed in bug #193903. I will investigate that first. 1500045 2 mcatanzaro 2019-01-30 09:54:45 -0800 Carlos Garcia doesn't want to do this. Closing.