RESOLVED FIXED 28754
Positioned, compositing child jumps around as opacity transition runs
https://bugs.webkit.org/show_bug.cgi?id=28754
Summary Positioned, compositing child jumps around as opacity transition runs
Simon Fraser (smfr)
Reported 2009-08-26 15:57:53 PDT
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.
Attachments
Testcase (1.88 KB, text/html)
2009-08-26 15:57 PDT, Simon Fraser (smfr)
no flags
Simpler testcase (1.06 KB, text/html)
2009-08-28 17:24 PDT, Simon Fraser (smfr)
no flags
Patch, testcases, changelogs (11.94 KB, patch)
2009-08-28 18:43 PDT, Simon Fraser (smfr)
mitz: review+
Simon Fraser (smfr)
Comment 1 2009-08-26 15:58:20 PDT
Simon Fraser (smfr)
Comment 2 2009-08-28 17:24:38 PDT
Created attachment 38765 [details] Simpler testcase
Simon Fraser (smfr)
Comment 3 2009-08-28 18:43:00 PDT
Created attachment 38767 [details] Patch, testcases, changelogs
mitz
Comment 4 2009-08-29 15:45:42 PDT
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.
Simon Fraser (smfr)
Comment 5 2009-08-31 11:38:30 PDT
Note You need to log in before you can comment on or make changes to this bug.