Bug 89712 - [chromium] Initialize compositor's visibility state upon initialization
Summary: [chromium] Initialize compositor's visibility state upon initialization
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: James Robinson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-21 17:10 PDT by James Robinson
Modified: 2012-06-21 19:39 PDT (History)
3 users (show)

See Also:

Attachments
Patch (2.04 KB, patch)
2012-06-21 17:12 PDT, James Robinson 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Robinson 2012-06-21 17:10:16 PDT 
[chromium] Initialize compositor's visibility state upon initialization
Comment 1 James Robinson 2012-06-21 17:12:34 PDT 
Created attachment 148916 [details]
Patch
Comment 2 Adrienne Walker 2012-06-21 17:15:46 PDT 
Comment on attachment 148916 [details]
Patch

R=me.  I'm surprised we're not burned more often by lazily created objects that miss state set earlier.
Comment 3 James Robinson 2012-06-21 17:18:04 PDT 
Comment on attachment 148916 [details]
Patch

Me too. We should fix this in a structural way (not sure exactly what that is yet).
Comment 4 WebKit Review Bot 2012-06-21 19:39:38 PDT 
Comment on attachment 148916 [details]
Patch

Clearing flags on attachment: 148916

Committed r120995: <http://trac.webkit.org/changeset/120995>
Comment 5 WebKit Review Bot 2012-06-21 19:39:43 PDT 
All reviewed patches have been landed.  Closing bug.