<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Avoid calling updateCompositingLayers() more than once before each render"
href="https://bugs.webkit.org/show_bug.cgi?id=84393#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Avoid calling updateCompositingLayers() more than once before each render"
href="https://bugs.webkit.org/show_bug.cgi?id=84393">bug 84393</a>
from <span class="vcard"><a class="email" href="mailto:simon.fraser@apple.com" title="Simon Fraser (smfr) <simon.fraser@apple.com>"> <span class="fn">Simon Fraser (smfr)</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=84393#c15">comment #15</a>)
<span class="quote">> So we need an in-WebKit data structure for tracking repaints</span >
We have this already (we accumulate dirty rects in GraphicsLayers). The problems are:
1. we dirty during layout, and dirtying assumes that you can find the relevant repaintContainer (which is a compositing layer) and compute a dirty rect relative to it.
2. RenderLayers cache repaint rects, which will also go stale if their repaint container changes because of compositing updates.
So we need a data structure that hangs off the render tree that tracks repaints, and can track them sensibly across multiple layouts, in a compositing-independent way.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>