Closed Bug 379891 Opened 19 years ago Closed 4 years ago

JS Strict warnings for content shouldn't get dumped to terminal

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: Dolske, Unassigned)

References

(
URL
)

Details

I have javascript.options.strict enabled in Firefox. This results in spewage to the terminal (stdout/stderr) when browsing, and makes watching the other spewage rather difficult (asserts, warnings and errors, oh my!). CNN is a good example of this. It would make more sense to me to only logchrome's strict errors to the terminal. Using the Error Console for warnings from content is sufficient (since that's where interested web authors will be looking anyway). If JS isn't aware of chrome/content at the logging level, it would probably be better to just not log anything to the terminal. In bug 248528 comment 12, Brendan makes a suggestion that might be a functional equivalent to this.
Blocks: 296661
Assignee: general → nobody

No longer valid after bug 1619177.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.