[webkit-dev] spamming the developer console

[Ryosuke Niwa]

On Fri, May 11, 2012 at 2:21 PM, Ojan Vafai <ojan at chromium.org> wrote:

> The amount of spam we throw in the developer console has grown quite a bit.
>
> spam == things logged to the console that web developers have no control
> over
>
> Unlike uncaught javascript exceptions (which can easily just be caught),
> there is no way to prevent the following from cluttering your console:
> -clientX/clientY deprecation warning
> -setting the fragment on a frame URL [1]
> -loading a resource disallowed by CSP
> -attempting to load a resource (e.g. in an image or iframe) that doesn't
> exist
>
> These warnings are not developer friendly. The equivalent would be to have
> compiler warnings that you are unable to turn off. It clutters the console
> and makes many console use-cases harder (e.g. console.log style debugging).
> We need a better solution.
>

But isn't the whole point of emitting warnings for clientX/clientY, etc...
is to nag developers about removing them?

FWIW, Firefox's console tends to be much noisier.

- Ryosuke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20120511/2dbf6896/attachment.html>