Closed
Bug 1145394
Opened 10 years ago
Closed 10 years ago
Ensure all JS in m-c is parseable
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
Firefox 39
Tracking | Status | |
---|---|---|
firefox39 | --- | fixed |
People
(Reporter: billm, Assigned: billm)
References
Details
Attachments
(3 files)
6.47 KB,
patch
|
Gavin
:
review+
|
Details | Diff | Splinter Review |
2.08 KB,
patch
|
Gavin
:
review+
|
Details | Diff | Splinter Review |
1.54 KB,
patch
|
Gavin
:
review+
fabrice
:
review+
|
Details | Diff | Splinter Review |
I would like to be able to parse all .js and .jsm files in the tree. The patches in here make that happen.
Assignee | ||
Comment 1•10 years ago
|
||
The way we were using the preprocessor in these two files (with comments interleaved) was messing up my broken preprocessing code. This patch switches these two cases to use AppConstants.
Attachment #8580325 -
Flags: review?(gavin.sharp)
Assignee | ||
Comment 2•10 years ago
|
||
This code must be unused or something. It's not syntactically correct. This patch fixes it.
Attachment #8580326 -
Flags: review?(gavin.sharp)
Assignee | ||
Comment 3•10 years ago
|
||
Having the executable bit set on these JS files is screwing up my heuristics for finding JS code. There's no reason for these files to be executable, so I think we should turn it off.
Fabrice, can you "review" the DOM changes and Gavin the rest?
Attachment #8580328 -
Flags: review?(gavin.sharp)
Attachment #8580328 -
Flags: review?(fabrice)
Comment 4•10 years ago
|
||
Comment on attachment 8580328 [details] [diff] [review]
Remove executable permission from some js files
Not sure how that happened in the first place!
Attachment #8580328 -
Flags: review?(fabrice) → review+
Updated•10 years ago
|
Attachment #8580328 -
Flags: review?(gavin.sharp) → review+
Comment 5•10 years ago
|
||
Comment on attachment 8580326 [details] [diff] [review]
Fix code that is broken or unused
Can you file a bug on removing CRH_DIALOG_TREE_VIEW-related code?
Attachment #8580326 -
Flags: review?(gavin.sharp) → review+
Updated•10 years ago
|
Attachment #8580325 -
Flags: review?(gavin.sharp) → review+
Assignee | ||
Comment 6•10 years ago
|
||
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/8626a98a34d8
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/f7c5c5c8bdff
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/72c740d37eb9
Filed bug 1145735 for CRH_DIALOG_TREE_VIEW.
Comment 7•10 years ago
|
||
Rev 8626a98a34d8 backed out for mochitest-bc exceptions.
https://hg.mozilla.org/integration/mozilla-inbound/rev/7ff3c70a5ad2
https://treeherder.mozilla.org/logviewer.html#?job_id=7865945&repo=mozilla-inbound
Keywords: leave-open
Comment 8•10 years ago
|
||
Oh, looks like there are a bunch of other #ifdefs in applications.js...
Assignee | ||
Comment 9•10 years ago
|
||
Oops. These files are actually pretty hard cases for eliminating the preprocessor since they use #expand and HAVE_SHELL_SERVICE (not sure what that is). I'll re-land when I can but leave the * annotations in the jar.mn files.
Comment 10•10 years ago
|
||
HAVE_SHELL_SERVICE is basically trying to exclude MOZ_WIDGET_QT (and maybe OS2 and other non-supported things), so AppConstants.platform won't quite work. We might be able to just get rid of it entirely.
For the #expands its easy enough to add MOZ_APP_NAME and MOZ_MACBUNDLE_NAME to AppConstants.
Comment 11•10 years ago
|
||
(Don't need to chase those in this bug, certainly.)
Comment 12•10 years ago
|
||
Comment 13•10 years ago
|
||
Commit pushed to master at https://github.com/mozilla/addon-sdk
https://github.com/mozilla/addon-sdk/commit/e8c963fce3ff1e9011d8931d1acc68b9703991f1
Bug 1145394 - Fix unparseable JS code (r=gavin)
Comment 14•10 years ago
|
||
I accidentally clobbered the addon-sdk part of this when I landed bug 1146943 today so relanded as https://hg.mozilla.org/integration/fx-team/rev/692ec0a78180.
Comment 15•10 years ago
|
||
Assignee | ||
Comment 16•10 years ago
|
||
Keywords: leave-open
Comment 17•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox39:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 39
You need to log in
before you can comment on or make changes to this bug.
Description
•