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
This removes an unnecessary level of indirection by replacing all
nsStringGlue.h instances with just nsString.h.
--HG--
extra : rebase_source : 340989240af4018f3ebfd92826ae11b0cb46d019
Replace it with NS_INTERFACE_MAP_BEGIN_CYCLE_COLLECTION, because it
has been the same for a while.
MozReview-Commit-ID: 5agRGFyUry1
--HG--
extra : rebase_source : 5388c56b2f6905c6ef969150f0c5b77bf247624d
dom/asmjscache/AsmJSCache.cpp:371:3 [-Wunused-member-function] unused member function 'IsOnOwningThread'
dom/cache/DBSchema.cpp:303:3 [-Wunused-member-function] unused member function 'IdCount'
dom/filesystem/GetFilesHelper.cpp:26:3 [-Wunused-member-function] unused member function 'ReleaseRunnable'
dom/webbrowserpersist/WebBrowserPersistLocalDocument.cpp:298:10 [-Wunused-member-function] unused member function 'IsFlagSet'
MozReview-Commit-ID: 2A11iqF7u9X
--HG--
extra : source : abc07611c7cc994685cf151a47c90e3e9d3712a1
extra : intermediate-source : 44a7cfc31d995c50846aec3050514aea70ba2e2f
extra : histedit_source : 2ed361299e763d969619d3916ff20d9553d620f2
For the Quatum DOM project, it's better to work in terms of event targets than
threads. This patch converts DOM code to operate on event targets rather than
threads, when possible.
MozReview-Commit-ID: 5FgvpKadUA2
As long as Directory objects can be constructed in the content process, trying
to access the file system conceptually does not make sense because of
sandboxing. The canary in the coal mine for this was tests which started
crashing on Directory construction as we further locked down read access in the
sandbox.
MozReview-Commit-ID: HZitALYpO5H
--HG--
extra : rebase_source : 1f7e0361e40e45a9c23d5d78bdcdc1696d44d298
The declarations of their refcounting methods already includes an owning
thread, so let's just piggyback on top of that to assert their owning
thread, rather than having separate fields and tests.
