[Webkit-unassigned] [Bug 156001] Web Inspector: Console is unusable on sites with frequent Blocked Messages (theverge.com)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Feb 13 10:40:18 PST 2017


--- Comment #8 from Michael Bishop <mbish2013 at gmail.com> ---
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #5)
> > > 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.
> Related Chromium thread that resolves exactly this issue in the Chrome fork
> of webkit: https://bugs.chromium.org/p/chromium/issues/detail?id=17325
> 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.

Edit: Actually including the JSFidddle. :) 


You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170213/6645d692/attachment.html>

More information about the webkit-unassigned mailing list