<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Setter on style element's textContent or cssText doesn't trigger style recalc"
href="https://bugs.webkit.org/show_bug.cgi?id=160331#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Setter on style element's textContent or cssText doesn't trigger style recalc"
href="https://bugs.webkit.org/show_bug.cgi?id=160331">bug 160331</a>
from <span class="vcard"><a class="email" href="mailto:rniwa@webkit.org" title="Ryosuke Niwa <rniwa@webkit.org>"> <span class="fn">Ryosuke Niwa</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=160331#c15">comment #15</a>)
<span class="quote">> Sure, there are some known and likely many unknown shadow DOM related bugs
> and inefficiencies.</span >
Well, my point about the architectural problem is that basically everywhere we call Document::styleResolverChanged is a place where we might need to find a StyleResolver in every shadow tree and trigger a similar style recalc logic.</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>