[webkit-dev] spamming the developer console
rniwa at webkit.org
Fri May 11 14:27:15 PDT 2012
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
> there is no way to prevent the following from cluttering your console:
> -clientX/clientY deprecation warning
> -setting the fragment on a frame URL 
> -loading a resource disallowed by CSP
> -attempting to load a resource (e.g. in an image or iframe) that doesn't
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev