Summary: | [chromium] Pass setVisibility to CCLayerTreeHostImpl regardless of LRC initialization status | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Nat Duca <nduca> | ||||||||
Component: | New Bugs | Assignee: | Nat Duca <nduca> | ||||||||
Status: | RESOLVED FIXED | ||||||||||
Severity: | Normal | CC: | cc-bugs, jamesr, webkit.review.bot | ||||||||
Priority: | P2 | ||||||||||
Version: | 528+ (Nightly build) | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Attachments: |
|
Description
Nat Duca
2012-03-08 02:43:40 PST
Created attachment 130799 [details]
Patch
As part of re-working the compositeAndReadback flow, I am trying to write a unit test that fails for the existing broken case. In doing that, I got bitten by the visibility call behaving differently during initialization. So, I'm thinking, can we just make it all the time? Created attachment 130804 [details]
null check during initialize
Comment on attachment 130804 [details] null check during initialize View in context: https://bugs.webkit.org/attachment.cgi?id=130804&action=review OK > Source/WebCore/platform/graphics/chromium/cc/CCLayerTreeHostImpl.cpp:399 > + if (visible && m_layerRenderer && m_layerRenderer->capabilities().usingPartialSwap) since we're also null checking m_layerRenderer on line 394 probably better to just null check it and return above that line instead of checking it twice Created attachment 130907 [details]
Normalize SingleThreadProxy behavior also
Comment on attachment 130907 [details]
Normalize SingleThreadProxy behavior also
Putting r? again because I made a similar change to CCSingleThreadProxy::setVisible
Comment on attachment 130907 [details]
Normalize SingleThreadProxy behavior also
OK
Comment on attachment 130907 [details] Normalize SingleThreadProxy behavior also Clearing flags on attachment: 130907 Committed r110255: <http://trac.webkit.org/changeset/110255> All reviewed patches have been landed. Closing bug. |