Lately, the stricter checks from JS engines produced many warnings during the test suite run (|make mozmill|) of locally built DEBUG BUILD of C-C thunderbird.
These in themselves are very good to make code better, more robust, etc. However, today I noticed a few problems of line numbers thus reported in the warnings. Has anyone noticed similar issues? Cases in point: Please see Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1081767 Bug 1081767 JavaScript error: chrome://messenger/content/nsContextMenu.js, line 693: TypeError: item is null In this bugzilla, line 693 is actually out of range for the file reported. The file is much shorter. Worse, in another part of the log, I see line 694 reported for this same error. It looks as though there is an uninitialized variable or something (that gets referenced when it has different values when these warnings are printed. https://bugzilla.mozilla.org/show_bug.cgi?id=1081765 Bug 1081765 JavaScript strict warning: chrome://messenger/content/nsContextMenu.js, line 103: ReferenceError: reference to undefined property this.onEditableArea When I look at line 103, the line again is an empty line, and I look at the previous line, but there does not seem to any mention of this.onEditableArea on that line. I suspect that the line numbers are incorrect in these cases. Anyone notice the similar line # issues? The C-C source tree was refreshed yesterday. (I know that copy of M-C subtree in C-C is synched, but still lag the true M-C tree a little bit, and so if this issue is fixed in true M-C tree already, please disregard this message.) TIA _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
