> 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. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
