I agree. We should do this.
I would prefer to see us not do any work at all to report our errors if it's a release build, rather than filtering out at the last possible moment. But I wonder if this info is useful for tech support, in which case having a way to turn them on would be useful.
These errors are incredibly helpful in nightlys if nothing else.... Having a way for bug reporters to be able to provide that information would be good.
Oh, definitely. We should probably have them on in milestones, too. We should provide an easy way for distributors to turn them off, though.
Hiding the bugs under the carpet won't make them go away. I would find it more embarrassing to hide them than to have them to begin with. Oh yeah, and not being able to hide them is an extra incentive to fix ;-)
I couldn't agree more with Bob.
nsbeta1+ per Nav triage team.
Mass move of nsbeta1+ bugs that didn't have a valid MachV milestone to mozilla1.0.
Comment on attachment 71244 [details] [diff] [review] patch sr=hewitt
Comment on attachment 71244 [details] [diff] [review] patch email@example.com with the 'from chrome' (or similar) text change we discussed on IRC.
a=asa (on behalf of drivers) for checkin to 0.9.9
reopening, review please
Please file a new bug for nits...thanks. The capitalized S does not need to be fixed. This is debug UI!!