<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Cached external stylesheets do not (re)output parser warnings for stylesheet to console"
href="https://bugs.webkit.org/show_bug.cgi?id=147721#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Cached external stylesheets do not (re)output parser warnings for stylesheet to console"
href="https://bugs.webkit.org/show_bug.cgi?id=147721">bug 147721</a>
from <span class="vcard"><a class="email" href="mailto:bburg@apple.com" title="Brian Burg <bburg@apple.com>"> <span class="fn">Brian Burg</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=147721#c2">comment #2</a>)
<span class="quote">> I suppose the right approach here depends what the inspector intention is.
> Should it accurately report what happens during the page load? We don't
> parse the sheet if it is cached so there are no parse errors. Or should it
> show maximum amount of information about the page resources?</span >
IMO, not reparsing is a performance optimization that should not be surfaced. I think the Inspector should show the same parse errors, whether or not the resource was cached- this is what happens for other cached resources that have syntax errors, like JS.
The inspector does not currently show whether the stylesheet was reparsed or not. (In fact, it gets reparsed by the inspector many times, but this is transparent.) Joe and I had to dig into WebCore and use breakpoints to get some ground truth on whether something was reparsed.</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>