Bug 193972
| Summary: | [GTK] Temporarily switch default hardware acceleration policy to WEBKIT_HARDWARE_ACCELERATION_POLICY_NEVER | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | bugs-noreply, magomez, mcatanzaro, zan |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Bug Depends on: | |||
| Bug Blocks: | 192523 | ||
Michael Catanzaro
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Michael Catanzaro
I wonder if this has been fixed in bug #193903. I will investigate that first.
Michael Catanzaro
Carlos Garcia doesn't want to do this. Closing.