Debug builds already have this option turned on automatically
(http://lxr.mozilla.org/seamonkey/source/dom/src/base/nsJSEnvironment.cpp#324)
and obviously that's not helping much.
Are the offending developers ignoring the debug output? Then a developer.js
pref file won't help. Are they using release builds to write XUL? A
non-packaged developer.js won't help. It only helps in the case where XUL
developers build their own optimized builds, and don't ignore the javascript
console.
-Dan Veditz
Seth Spitzer wrote:
>
> we could create mozilla/modules/libpref/src/init/developer.js and
> default that pref to be true.
>
> we just wouldn't package it by default, so only developers would have
> it. (official builds would not.)
>
> -Seth
>
> Henrik Gemal wrote:
>
> > Whenever some xul or javascript is checked into mozilla, I'm able to
> > report at least 2 - 3 new javascript strict warnings bugs.
> >
> > Couldn't the developers (and perhaps others) please add the following
> > line to thier prefs.js file, so we could avoid all the strict warning
> > fixup...:
> >
> > user_pref("javascript.options.strict", true);
> >
> > Currently we have 56 bugs open on strict warnings. It takes a extra
> > second to fix the warning before checkin and at least 3 days to fix the
> > warning after the first checkin.
> >
> > This will save time for both me, the developers and the reviewers!
> >
> > --
> > Henrik Gemal, [EMAIL PROTECTED]
> > Webmail Evangelist
> > TDC Internet
> >
> > http://card.gemal.dk
> >
> >
> >
> >
