<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:mbish2013@gmail.com" title="Michael Bishop <mbish2013@gmail.com>"> <span class="fn">Michael Bishop</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Console is unusable on sites with frequent Blocked Messages (theverge.com)"
href="https://bugs.webkit.org/show_bug.cgi?id=156001">bug 156001</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>mbish2013@gmail.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Console is unusable on sites with frequent Blocked Messages (theverge.com)"
href="https://bugs.webkit.org/show_bug.cgi?id=156001#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Console is unusable on sites with frequent Blocked Messages (theverge.com)"
href="https://bugs.webkit.org/show_bug.cgi?id=156001">bug 156001</a>
from <span class="vcard"><a class="email" href="mailto:mbish2013@gmail.com" title="Michael Bishop <mbish2013@gmail.com>"> <span class="fn">Michael Bishop</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=156001#c6">comment #6</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=156001#c5">comment #5</a>)
> > Making console only render messages that are in the viewport would solve
> > this as well.
>
> I don't think that would help here. The issue here is the deluge of
> "blocked" messages makes the console unusable. Having the console be fast
> but still filled with messages would still be unusable in this respect.</span >
Related Chromium thread that resolves exactly this issue in the Chrome fork of webkit: <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=17325">https://bugs.chromium.org/p/chromium/issues/detail?id=17325</a>
The issue stems from cross-domain iframe access attempts that violate the same-origin policy; even when wrapped in a try/catch block, this message is still output. See the following jsfiddle for a simple example showing that the try/catch logic evaluates correctly, but the access attempt is still logged despite the catch.
There's a lot of interest from the adtech industry in resolving this issue, since it makes debugging in Safari browsers difficult to impossible.</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>