Bug 25282 – RenderBox::outlineBoundsForRepaint should use the repaintContainer

• Status: RESOLVED
• Resolution: FIXED
• Component: Layout and Rendering

[Simon Fraser (smfr)]

RenderBox::outlineBoundsForRepaint does:

    FloatQuad absOutlineQuad = localToAbsoluteQuad(FloatRect(box));
    box = absOutlineQuad.enclosingBoundingBox();

ignoring the repaintContainer. Bad RenderBox!

[Simon Fraser (smfr)]

Created attachment 29599 [details]
Patch, testcases, changelog

[Eric Seidel (no email)]

I need more context to understand your test cases.  Could you please provide more description in the ChangeLogs or, better yet, in the tests themselves?  What was the old behavior? what is the next behavior?  How is this testing with repaint containers?

[Simon Fraser (smfr)]

In the changelog, I refer to bug 12885, which is the fix that added the original version of outlineBoundsForRepaint() (then called absoluteOutlineBox()). That changelog says:

+        Changed repaintAfterLayoutIfNeeded() to take, in addition to the clipped overflow
+        rect, the unclipped border box plus outline, and to repaint any areas that
+        were added or removed from that box, in addition to any areas added or removed
+        from the clipped overflow rect.

The testcases I added here clone two of the testcases that were added for that fix, and wrap the content in a div with a 3d-transform. That will force that div into a compositing layer, and hence test the need to compute the repaint rects relative to the container.

[Eric Seidel (no email)]

Comment on attachment 29599 [details]
Patch, testcases, changelog

Verbage saying "this only fails on accellerated_compositing builds" would be useful I think.  r=me

[Simon Fraser (smfr)]

http://trac.webkit.org/changeset/42675