Closed Bug 1039725 Opened 10 years ago Closed 10 years ago

hide css errors unless running with --verbose

Categories

(Add-on SDK Graveyard :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: zombie, Unassigned)

References

Details

a common complaint from developers, "i can't see my addon tree for the CSS error forest".

set layout.css.report_errors to false

this should probably be a jpm bug in addition/instead of cfx..
I think CSS errors should definitely be removed when tests are executed, by default.

However I'm not totally convinced about set such preference running the add-on, because is made for debugging, and sometimes check that CSS / HTML stuff were wrong helped me to adjust page-mod add-ons.
Plus, set the preference it would change the behavior of the Browser Console, not only our terminal dump, where I think for the Browser Console we should use the value of the profile where is running, that can be changed by the browser console interface or from `about:config`.

I would definitely prefer filter out the CSS / HTML error only from our terminal dump of the browser console: in that case I totally agree to remove them, without set such preference.

We should focus on jpm however, and leave the cfx as is.
Priority: -- → P2
Sorry we won't be releasing any new versions of cfx, jpm is the replacement https://www.npmjs.com/package/jpm
Blocks: cfx.py
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.