Bug 44367
Summary: | [Qt] Accelerated Compositing is off by default even ACCELERATED_COMPOSITING flag is set | ||
---|---|---|---|
Product: | WebKit | Reporter: | Dan <dan.strashenko> |
Component: | WebKit Misc. | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | benjamin |
Priority: | P2 | Keywords: | Qt, QtTriaged |
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | Windows XP |
Dan
Qt Webkit port of trunk r64996
running test cases using "WebKitTools\scripts\run-launcher" on Windows
QWebPageClient's implementation of allowsAcceleratedCompositing returns false even though ACCELERATED_COMPOSITING flag is defined.
The result is RenderLayerCompositor is not creating RenderLayerBacking for the layer with transition or animation style set.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Dan
Ok, the reason for QtTestBrowser not to use accelerated composition is that it has to run with "-graphicsbased" flag but by default "run-launcher" does not specify it even when compiled with ACCELERATED_COMPOSITING flag. So the issue is rather with QtTestBrowser or lack of documentation on accelerated composition.
QtTestBrowser could change this pure run-time verification
if (args.contains("-graphicsbased"))
windowOptions.useGraphicsView = true;
to be based on compile time flag ACCELERATED_COMPOSITING.
Thanks.
Benjamin Poulain
Please follow this to report bugs on QtWebKit: http://trac.webkit.org/wiki/QtWebKitBugs
Closing as invalid, just a missunderstanding about accelerated compositing.