Bug 1031490 - Remove references to test-harness/run-tests
Merge pull request #1525 from erikvold/1031490

Bug 1031490 - Remove references to test-harness/run-tests r=@ZER0
bug 1026543 - expose tab.readyState
Merge pull request #1517 from zombie/1026543-tab-readyState

bug 1026543 - expose tab.readyState property, r=@erikvold
Bug 1031575 - change the add-on entry point in sdk/addon/runner instead of on the cfx/python side
Bug 1010616 - PredicateContext does not set linkURL of parentNodes
Merge pull request #1523 from spammail495/master

Bug 1010616 - PredicateContext does not set linkURL of parentNodes, r=@zombie
Bug 1031082 - Worker's ports should have event listeners unbound after destruction.
bug 1023326 - use frame scripts for tab content events
Merge pull request #1510 from zombie/1023326-tab-events

bug 1023326 - use frame scripts for tab content events, r=@Mossop
Revert "bug 1023326 - use frame scripts for tab content events"
Merge pull request #1531 from mozilla/revert-1510-1023326-tab-events

Revert "bug 1023326 - use frame scripts for tab content events"
Bug 1032606 - remove extend function from sdk/test
Merge pull request #1532 from erikvold/1032606

Bug 1032606 - remove extend function from sdk/test r=@jsantell
Bug 1032731 - hack sdk/deprecated/unit-test-finder to work with new loader
Merge pull request #1533 from erikvold/1032731

Bug 1032731 - hack sdk/deprecated/unit-test-finder to work with new loader r=@jsantell
bug 1023326 - fix chrome tabs, brittle test
Bug 1001833 - "TypeError: can't access dead object" due leaks of event/dom and event/chrome modules

- Ensured listeners and observers are removed once the add-on is disabled / uninstalled
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.
Revert "Revert "bug 1023326 - use frame scripts for tab content events""