don't printf CSS errors to the console (stdout) in debug builds

VERIFIED FIXED in mozilla1.9.1a2

Status

()

VERIFIED FIXED
11 years ago
11 years ago

People

(Reporter: dbaron, Assigned: dbaron)

Tracking

Trunk
mozilla1.9.1a2
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Created attachment 332557 [details] [diff] [review]
patch

At the summit people were complaining about the console output noise caused by printing CSS errors to the console.  This removes that printing.
Attachment #332557 - Flags: superreview?(bzbarsky)
Attachment #332557 - Flags: review?(bzbarsky)
Comment on attachment 332557 [details] [diff] [review]
patch

r+sr=bzbarsky, but it might be nice to be able to condition this on an env var or something...  Either way.
Attachment #332557 - Flags: superreview?(bzbarsky)
Attachment #332557 - Flags: superreview+
Attachment #332557 - Flags: review?(bzbarsky)
Attachment #332557 - Flags: review+
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1a2pre) Gecko/2008080704 SeaMonkey/2.0a1pre] (home, debug) (W2Ksp4)

V.Fixed

NB: The CSS errors are still reported in the Error Console, as expected.
Blocks: 448156
Status: RESOLVED → VERIFIED
Summary: dont printf CSS errors to the console (stdout) in debug builds → don't printf CSS errors to the console (stdout) in debug builds
You need to log in before you can comment on or make changes to this bug.