Closed Bug 1096931 Opened 11 years ago Closed 11 years ago

"Web Console" (web JavaScript) spams the "Browser Console"(chrome JavaScript)

Categories

(DevTools :: Console, defect)

35 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 802543

People

(Reporter: tito.bouzout, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.111 Safari/537.36 Steps to reproduce: The "Web Console" is supposed to show errors of the actual page (web JavaScript). The "Browser Console" is supposed to show errors of the browser (chrome JavaScript) The problem is that the "Browser Console" also gets all errors of the "Web Console", then that amount of "console spam" blur and hides the important "chrome errors" 1. Open http://yahoo.com/ 2. CTLR+SHIFT+J (this will open the "Browser Console") 3. Enable all the console options for the sake of illustrating the problem 4. Clean the console with the "Clear" button. 3. Now paste the following "chrome JavaScript" (privileged JavaScript) in the "evaluator" (line that evaluates js when pressing enter.) setInterval(function(){ content.document.location.reload(); if( Math.floor(Math.random()*11) > 4) console.log('This is my very important log message from "privileged JavaScript", weee..') } , 2000); Actual results: what happens is that the opened site http://yahoo.com/ spams the "browser console" with tons of messages from "web console" and is almost impossible to see my "very important log message" from "chrome JavaScript" Expected results: I expected this console to not show any "web page messages", at the very least a button to "turn off" or filter messages from unprivileged JavaScript. Is complicated to debug extensions and browser functions.
Component: Untriaged → Developer Tools: Console
OS: Windows 7 → All
Hardware: x86_64 → All
Indeed, this is a long-standing issue.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.