| Summary: | Positioned, compositing child jumps around as opacity transition runs | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> | ||||||||
| Component: | Layout and Rendering | Assignee: | Simon Fraser (smfr) <simon.fraser> | ||||||||
| Status: | RESOLVED FIXED | ||||||||||
| Severity: | Normal | Keywords: | InRadar | ||||||||
| Priority: | P2 | ||||||||||
| Version: | 528+ (Nightly build) | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | OS X 10.5 | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 38765 [details]
Simpler testcase
Created attachment 38767 [details]
Patch, testcases, changelogs
Comment on attachment 38767 [details] Patch, testcases, changelogs > + for ( ; curr && !isPositionedContainer(curr); curr = curr->parent()) > + { } Is this the WebKit style convention for empty loop bodies? It seems strange. > for ( ; curr && !curr->renderer()->isRenderView() && !curr->transform(); curr = curr->parent()) > - { } > + { } Ditto. > + RenderLayer* positionedAncestor = enclosingPositionedAncestor(); I think you can call parentLayer->enclosingPositionedAncestor() instead. > + int thisX = 0, thisY = 0; Please define each variable on a separate line. > + convertToLayerCoords(positionedAncestor, thisX, thisY); > + > + int ancestorX = 0, ancestorY = 0; Separate lines, please. |
Created attachment 38643 [details] Testcase The attached testcase shows a bug where the inner child renders in the wrong place while the opacity transition is running, when accelerated compositing is enabled.