Commit Graph

20 Commits

Author SHA1 Message Date
Florian Quèze
f1a55f73f8 Bug 1440284 - change this.EXPORTED_SYMBOLS back to var EXPORTED_SYMBOLS in JS modules, r=mccr8. 2018-02-23 20:50:01 +01:00
Andrew McCreight
272cee1e65 Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian
This patch was autogenerated by my decomponents.py

It covers almost every file with the extension js, jsm, html, py,
xhtml, or xul.

It removes blank lines after removed lines, when the removed lines are
preceded by either blank lines or the start of a new block. The "start
of a new block" is defined fairly hackily: either the line starts with
//, ends with */, ends with {, <![CDATA[, """ or '''. The first two
cover comments, the third one covers JS, the fourth covers JS embedded
in XUL, and the final two cover JS embedded in Python. This also
applies if the removed line was the first line of the file.

It covers the pattern matching cases like "var {classes: Cc,
interfaces: Ci, utils: Cu, results: Cr} = Components;". It'll remove
the entire thing if they are all either Ci, Cr, Cc or Cu, or it will
remove the appropriate ones and leave the residue behind. If there's
only one behind, then it will turn it into a normal, non-pattern
matching variable definition. (For instance, "const { classes: Cc,
Constructor: CC, interfaces: Ci, utils: Cu } = Components" becomes
"const CC = Components.Constructor".)

MozReview-Commit-ID: DeSHcClQ7cG
2018-02-06 09:36:57 -08:00
Kris Maglione
0bb74efdf1 Bug 1431533: Part 5a - Auto-rewrite code to use ChromeUtils import methods. r=florian
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm

MozReview-Commit-ID: 1Nc3XDu0wGl
2018-01-29 15:20:18 -08:00
Cosmin Sabou
f09d6d985d Backed out 3 changesets (bug 1431533) for Android mochitest failures on testEventDispatcher on a CLOSED TREE
Backed out changeset a1eca62826a1 (bug 1431533)
Backed out changeset 34c999fa006b (bug 1431533)
Backed out changeset e2674287e57f (bug 1431533)
2018-01-30 07:17:48 +02:00
Kris Maglione
fd67f090b2 Bug 1431533: Part 5a - Auto-rewrite code to use ChromeUtils import methods. r=florian
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm

MozReview-Commit-ID: 1Nc3XDu0wGl
2018-01-29 15:20:18 -08:00
Brindusan Cristian
483ba301cb Backed out 2 changesets (bug 1431533) for ESlint failures on a CLOSED TREE
Backed out changeset 6e56f4c8843e (bug 1431533)
Backed out changeset 12fc4dee861c (bug 1431533)
2018-01-30 02:32:43 +02:00
Kris Maglione
683a97d172 Bug 1431533: Part 5a - Auto-rewrite code to use ChromeUtils import methods. r=florian
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm

MozReview-Commit-ID: 1Nc3XDu0wGl
2018-01-29 15:20:18 -08:00
Ryan VanderMeulen
15f7fec809 Bug 1370122 - Update pdf.js to version 1.8.423. r=bdahl 2017-06-04 21:38:45 -04:00
Ryan VanderMeulen
6634e4746a Bug 1366004 - Update pdf.js to version 1.8.363. r=bdahl 2017-05-18 13:40:06 -04:00
Ryan VanderMeulen
92a1db5da0 Bug 1335048 - Update pdf.js to version 1.7.235. r=bdahl 2017-01-23 15:32:49 -05:00
Ryan VanderMeulen
2bf465d6c3 Bug 1334363 - Update pdf.js to version 1.7.227. r=bdahl 2017-01-26 21:35:12 -05:00
Ryan VanderMeulen
0b71fbb4b1 Bug 1326340 - Update pdf.js to version 1.6.418. r=bdahl, r=Mossop 2016-12-29 22:08:13 -05:00
Phil Ringnalda
d6d6acca75 Backed out changeset 6f1dd8377713 (bug 1326340) for browser_parsable_css.js failure
MozReview-Commit-ID: KVUOe1Pkiyq
2016-12-29 21:05:04 -08:00
Ryan VanderMeulen
77abf56806 Bug 1326340 - Update pdf.js to version 1.6.418. r=bdahl 2016-12-29 22:08:13 -05:00
Ryan VanderMeulen
05c4b1c33d Bug 1226621 - Update pdf.js to version 1.3.14. r=bdahl 2015-11-20 11:32:09 -05:00
Ryan VanderMeulen
e91182fe60 Bug 1117757 - Update pdf.js to version 1.0.1040. r=yury, r=Mossop 2015-01-05 13:28:37 -05:00
Ryan VanderMeulen
bbefbc19b4 Bug 1064496 - Update pdf.js to version 1.0.801. r=yury, r=Mossop 2014-09-19 17:14:01 -04:00
Ryan VanderMeulen
c0576ad79c Bug 1042307 - Update pdf.js to version 1.0.473. r=yury, r=Mossop 2014-07-28 08:20:46 -04:00
Jim Blandy
39dc0c6097 Bug 914753: Make Emacs file variable header lines correct, or at least consistent. DONTBUILD r=ehsan
The -*- file variable lines -*- establish per-file settings that Emacs will
pick up. This patch makes the following changes to those lines (and touches
nothing else):

 - Never set the buffer's mode.

   Years ago, Emacs did not have a good JavaScript mode, so it made sense
   to use Java or C++ mode in .js files. However, Emacs has had js-mode for
   years now; it's perfectly serviceable, and is available and enabled by
   default in all major Emacs packagings.

   Selecting a mode in the -*- file variable line -*- is almost always the
   wrong thing to do anyway. It overrides Emacs's default choice, which is
   (now) reasonable; and even worse, it overrides settings the user might
   have made in their '.emacs' file for that file extension. It's only
   useful when there's something specific about that particular file that
   makes a particular mode appropriate.

 - Correctly propagate settings that establish the correct indentation
   level for this file: c-basic-offset and js2-basic-offset should be
   js-indent-level. Whatever value they're given should be preserved;
   different parts of our tree use different indentation styles.

 - We don't use tabs in Mozilla JS code. Always set indent-tabs-mode: nil.
   Remove tab-width: settings, at least in files that don't contain tab
   characters.

 - Remove js2-mode settings that belong in the user's .emacs file, like
   js2-skip-preprocessor-directives.
2014-06-24 22:12:07 -07:00
Ryan VanderMeulen
f0e34febd3 Bug 912006 - Update pdf.js to version 0.8.478. r=bdahl 2013-09-03 12:28:06 -04:00