RESOLVED FIXED 81354
[chromium] Don't occlude on main-thread behind layers/surfaces with impl-thread animations
https://bugs.webkit.org/show_bug.cgi?id=81354
Summary [chromium] Don't occlude on main-thread behind layers/surfaces with impl-thre...
Dana Jansens
Reported 2012-03-16 08:14:50 PDT
[chromium] Don't occlude behind layers/surfaces with impl-animating opacity on main thread
Attachments
Patch (18.78 KB, patch)
2012-03-16 10:55 PDT, Dana Jansens
no flags
Patch (18.59 KB, patch)
2012-03-16 11:19 PDT, Dana Jansens
no flags
Patch (24.13 KB, patch)
2012-03-16 12:07 PDT, Dana Jansens
no flags
Patch (24.08 KB, patch)
2012-03-16 15:13 PDT, Dana Jansens
no flags
Patch (23.96 KB, patch)
2012-03-18 16:40 PDT, Dana Jansens
no flags
Patch (23.95 KB, patch)
2012-03-18 16:55 PDT, Dana Jansens
no flags
Dana Jansens
Comment 1 2012-03-16 10:55:24 PDT
Dana Jansens
Comment 2 2012-03-16 11:19:16 PDT
Dana Jansens
Comment 3 2012-03-16 12:07:21 PDT
Created attachment 132340 [details] Patch Remove double negatives. Include logic so that we don't use occlusion within a space that we can't transform to. - i.e. If layer can't be transformed to target reliably, then occlusion in target can't be applied to the layer.
James Robinson
Comment 4 2012-03-16 15:05:29 PDT
Comment on attachment 132340 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=132340&action=review > Source/WebCore/platform/graphics/chromium/cc/CCOcclusionTracker.cpp:87 > +static inline bool layerOpacityKnown(const CCLayerImpl* /* layer */) { return true; } slightly better to omit the parameter name completely instead of commenting it out
Dana Jansens
Comment 5 2012-03-16 15:10:28 PDT
Comment on attachment 132340 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=132340&action=review >> Source/WebCore/platform/graphics/chromium/cc/CCOcclusionTracker.cpp:87 >> +static inline bool layerOpacityKnown(const CCLayerImpl* /* layer */) { return true; } > > slightly better to omit the parameter name completely instead of commenting it out Oh, yes definitely. I thought I saw that in the style guide but now I can't find it, so yay.
Dana Jansens
Comment 6 2012-03-16 15:13:52 PDT
Adrienne Walker
Comment 7 2012-03-16 15:51:49 PDT
Comment on attachment 132391 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=132391&action=review Looks good. R=me. > Source/WebCore/platform/graphics/chromium/cc/CCOcclusionTracker.cpp:91 > +static inline bool layerTransformsToScreenKnown(const CCLayerImpl* layer) { return true; } nit: unused param. > Source/WebCore/platform/graphics/chromium/cc/CCOcclusionTracker.cpp:98 > +static inline bool surfaceTransformsToScreenKnown(const CCRenderSurface* surface) { return true; } nit: unused param.
WebKit Review Bot
Comment 8 2012-03-16 17:18:46 PDT
Comment on attachment 132391 [details] Patch Attachment 132391 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/11968453
Dana Jansens
Comment 9 2012-03-18 16:40:57 PDT
Dana Jansens
Comment 10 2012-03-18 16:42:15 PDT
(In reply to comment #7) > (From update of attachment 132391 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=132391&action=review > > Looks good. R=me. Thanks for R! > > Source/WebCore/platform/graphics/chromium/cc/CCOcclusionTracker.cpp:91 > > +static inline bool layerTransformsToScreenKnown(const CCLayerImpl* layer) { return true; } > > nit: unused param. done > > Source/WebCore/platform/graphics/chromium/cc/CCOcclusionTracker.cpp:98 > > +static inline bool surfaceTransformsToScreenKnown(const CCRenderSurface* surface) { return true; } > > nit: unused param. done
Dana Jansens
Comment 11 2012-03-18 16:55:12 PDT
Created attachment 132509 [details] Patch rebase fixes
WebKit Review Bot
Comment 12 2012-03-18 18:07:33 PDT
Comment on attachment 132509 [details] Patch Clearing flags on attachment: 132509 Committed r111145: <http://trac.webkit.org/changeset/111145>
WebKit Review Bot
Comment 13 2012-03-18 18:07:39 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.