Bug 25052

Summary: With accelerated compositing, element positions are sometimes wrong.
Product: WebKit Reporter: Simon Fraser (smfr) <simon.fraser>
Component: Layout and RenderingAssignee: Simon Fraser (smfr) <simon.fraser>
Status: RESOLVED FIXED    
Severity: Normal    
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Mac   
OS: OS X 10.5   
Attachments:
Description Flags
Testcase
none
Patch, testcase, changelog darin: review+

Simon Fraser (smfr)
Reported 2009-04-04 22:22:13 PDT
When dynamically creating compositing layers, those layers are sometimes rendered in the wrong location.
Attachments
Testcase (1.17 KB, text/html)
2009-04-04 22:22 PDT, Simon Fraser (smfr) 		no flags
Details
Patch, testcase, changelog (8.29 KB, patch)
2009-04-05 18:49 PDT, Simon Fraser (smfr) 		darin: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Simon Fraser (smfr)
Comment 1 2009-04-04 22:22:49 PDT
Created attachment 29262 [details] Testcase
Simon Fraser (smfr)
Comment 2 2009-04-04 22:23:25 PDT
The problem here is that calculateCompositedBounds() is being called before we've determined which descendent layers are going to be compositing, so it returns the wrong answer.
Simon Fraser (smfr)
Comment 3 2009-04-05 18:49:56 PDT
Created attachment 29269 [details] Patch, testcase, changelog
Darin Adler
Comment 4 2009-04-06 09:02:18 PDT
Comment on attachment 29269 [details] Patch, testcase, changelog r=me
Simon Fraser (smfr)
Comment 5 2009-04-06 10:52:38 PDT
http://trac.webkit.org/changeset/42246
Note You need to log in before you can comment on or make changes to this bug.