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
--HG--
extra : rebase_source : d9c41878036c1ef7766ef5e91a7005025bc1d72b
The closeTab API call from UITour tells the parent process to close the current tab,
and doing so might end up disconnecting the message manager. This means that the
Promise that the ContentTask returns may never resolve. Instead of waiting for it
to resolve, we just wait for the TabClose event in the parent process.
MozReview-Commit-ID: Ci7ck9j4llK
--HG--
extra : rebase_source : a7d3625cc001072c097af5c3f78dd19585f68e4e
The UITour content API call uses sendAsyncMessage so we can't assume a synchronous close.
MozReview-Commit-ID: JXm2ztcLwW5
--HG--
extra : rebase_source : 0a7c3cdcd8e66eb33c56b143fe96b4f5dfd3bfc5
This gets us to 414 / 917 checks passing with e10s compared to non-e10s on my OS X machine.
--HG--
extra : commitid : 7VfxOGTGyvL
extra : rebase_source : 2fa3f0947ae80ff851b48206ac81cbadfa3c6b29