On a side note here, is there any usefulness of fixing these warnings (more specifically in web content than chrome content)? If you use any JS libraries like jQuery, they tend to spew a lot of these warnings. But take for example this code:
s = "Some text"; console.log(s); With javascript.options.strict set to true, it outputs "ReferenceError: assignment to undeclared variable s". Are there any advantages to actually fixing it? The code obviously works just fine either way. Wesley Hardman On 2014-12-19 15:19, Jason Orendorff wrote: > So if you go to about:config and set the javascript.options.strict pref, > you'll get warnings about accessing undefined properties. > > js> Math.TAU > undefined > /!\ ReferenceError: reference to undefined property Math.TAU > > (It says "ReferenceError", but your code still runs normally; it really is > just a warning.) > > Is anyone using this? Bug 1113380 points out that the rules about what kind > of code can cause a warning are a little weird (on purpose, I think). Maybe > it's time to retire this feature. > > https://bugzilla.mozilla.org/show_bug.cgi?id=1113380 > > Please speak up now, if you're still using it! > > -j > _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
