FYI, forwarding Ehsan’s reply: Begin forwarded message:
> From: Ehsan Akhgari <[email protected]> > Subject: Re: JavaScript (strict) Warning from FF mochitest-plain test. > Date: 2 Oct 2014 23:09:29 GMT+2 > To: Mike de Boer <[email protected]> > > Great! I'm all for this if we decide to act on the data. :-) > > (BTW this email was just sent to me, not sure if it went to the list or not > -- if you sent it through NNTP it probably did...) > > On Thu, Oct 2, 2014 at 5:06 PM, Mike de Boer <[email protected]> wrote: > On 02 Oct 2014, at 22:55, Ehsan Akhgari <[email protected]> wrote: >> >> Are we going to spend the time to fix these, however? > > I’d be up for that, certainly! > >> For context, for as long as I remember, if you kept the browser console >> open and used the browser, we'd occasionally report an unhandled chrome JS >> errors (for example when attempting to access properties off of null >> variables). And those are not even strict errors. >> >> I've occasionally filed bugs for them, but my impression was that unless I >> can construct a case for those warnings to map to a user visible bug, they >> would not be fixed. > > Hence my - perhaps controversial - idea to auto-create and auto-assign bugs. > So for new warnings that appear in the integration branch and m-c logs we > could even make those bugs block the bugs that introduced them. > > Mike. > > > > -- > Ehsan _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
