Bug 89712

Summary: [chromium] Initialize compositor's visibility state upon initialization
Product: WebKit Reporter: James Robinson <jamesr>
Component: New BugsAssignee: James Robinson <jamesr>
Status: RESOLVED FIXED    
Severity: Normal CC: enne, nduca, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

James Robinson
Reported 2012-06-21 17:10:16 PDT
[chromium] Initialize compositor's visibility state upon initialization
Attachments
Patch (2.04 KB, patch)
2012-06-21 17:12 PDT, James Robinson 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
James Robinson
Comment 1 2012-06-21 17:12:34 PDT
Created attachment 148916 [details] Patch
Adrienne Walker
Comment 2 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.
James Robinson
Comment 3 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).
WebKit Review Bot
Comment 4 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>
WebKit Review Bot
Comment 5 2012-06-21 19:39:43 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.