<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#c14">Comment # 14</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#c13">comment #13</a>)
<span class="quote">> Would it hurt compositing too much to make updating the compositing layers a
> completely separate pass from layout?</span >
No, that would be ideal. The problem is that we can't easily disassociate compositing layer updates from layout without losing repaints. If we stored repaints differently this would be easier to do.</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>