nsITabParent is exposed to frontend code and is generally used as a representation of a remote tab. We could just rename the interface to nsIBrowserParent and worry about it later, but I think it's better to rename the interface to nsIRemoteTab so that we can later work on splitting the interface away from the PBrowser protocol.
Note: Some frontend code refers to a TabParentId. This commit renames this to RemoteTabId. We need to figure out the purpose of TabId with fission.
Differential Revision: https://phabricator.services.mozilla.com/D28132
--HG--
rename : dom/interfaces/base/nsITabParent.idl => dom/interfaces/base/nsIRemoteTab.idl
extra : rebase_source : 9d8a1790a7bb10195ad063644d1a93d63b2afb72
- `Array.map` becomes `Array.from`
- Array copying via `Array.slice` becomes `Array.from`.
- `Array.forEach` that did not rely on closures becomes `for`-`of` loops.
- Anything else: `Array.X` becomes `Array.prototype.X`.
Complex cases:
dom/bindings/test/TestInterfaceJS.js and
dom/bindings/test/test_exception_options_from_jsimplemented.html
use `Array.indexOf` to generate an error with a specific error message.
Switched to `Array.prototype.forEach` to generate the same error.
js/src/jit-test/tests/basic/exception-column-number.js
In this test `Array.indexOf()` is used to generate an error. Since the
exact message doesn't matter, I switched to `Array.from()`.
Intentionally not changed:
editor/libeditor/tests/browserscope/lib/richtext/richtext/js/range.js
Did not modify because this is 3rd-party code and the code uses
feature detection as a fall back when Array generics are not used.
testing/talos/talos/tests/dromaeo/lib/mootools.js
Did not modify because mootools adds the `Array.slice` method to the
`Array` object.
Not changed because they check the implementation of Array generics:
js/src/jit-test/tests/basic/arrayNatives.js
js/src/jit-test/tests/basic/bug563243.js
js/src/jit-test/tests/basic/bug618853.js
js/src/jit-test/tests/basic/bug830967.js
js/src/jit-test/tests/jaeger/recompile/bug656753.js
js/src/jit-test/tests/self-hosting/alternate-static-and-instance-array-extras.js
js/src/tests/non262/Array/generics.js
js/src/tests/non262/Array/regress-415540.js
js/src/tests/non262/extensions/regress-355497.js
js/src/tests/non262/extensions/typedarray-set-neutering.js
Depends on D27802
Differential Revision: https://phabricator.services.mozilla.com/D27803
--HG--
extra : moz-landing-system : lando
This is split from the previous changeset since if we include dom/ the file size is too
large for phabricator to handle.
This is an autogenerated commit to handle scripts loading mochitest harness files, in
the simple case where the script src is on the same line as the tag.
This was generated with https://bug1544322.bmoattachments.org/attachment.cgi?id=9058170
using the `--part 2` argument.
Differential Revision: https://phabricator.services.mozilla.com/D27457
--HG--
extra : moz-landing-system : lando
Disabled plugin related tests.
Added `crashreporter` dependency for browser_restore_isAppTab.js.
Differential Revision: https://phabricator.services.mozilla.com/D25504
--HG--
extra : moz-landing-system : lando
1. If an object needs a custom function to |write|, it will be added to |memory|
in |JSStructuredCloneWriter| before calling the custom function. But in
JSStructuredCloneReader::startRead we did the opposite. This will cause
out-of-order if the custom function also writes some objects (e.g.
WriteStructuredCloneImageData). We fix this by keeping the same order in
|startRead|.
2. |JS_WriteTypedArray| should not call |writeTypedArray| directly, because it
will miss an entry in |memory| for the typed array itself. We fix this by calling
|startWrite| instead.
Differential Revision: https://phabricator.services.mozilla.com/D24670
--HG--
extra : moz-landing-system : lando
Replaced instances of callers in both C++ and JS files to query the state from the principal directly.
Differential Revision: https://phabricator.services.mozilla.com/D22532
--HG--
extra : moz-landing-system : lando
do not attempt to parse XHRs as XML if content-length=0, to prevent logging "no root element found" errors
Differential Revision: https://phabricator.services.mozilla.com/D23444
--HG--
extra : moz-landing-system : lando
Disable this test from `mochitest-browser-chrome`, possibly related to the wider audio/video issues in windows10-aarch64.
Differential Revision: https://phabricator.services.mozilla.com/D24090
--HG--
extra : moz-landing-system : lando
Disabled audio-related tests that have caused issues in the past:
- test_audioNotification.html
- test_audioNotificationSilent_audioFile.html
- test_audioNotificationSilent_webAudio.html
- test_audioNotificationStream.html
- test_audioNotificationStopOnNavigation.html
- test_audioNotificationWithEarlyPlay.html
Changes submitted as separate diff as per comments in https://phabricator.services.mozilla.com/D23744?id=76735#inline-137653
Differential Revision: https://phabricator.services.mozilla.com/D23750
--HG--
extra : moz-landing-system : lando
This test ensures that when meta viewport width is fixed, and a viewport
is requested with zero width, the viewport is assigned a height equal to
the scaled display height.
Differential Revision: https://phabricator.services.mozilla.com/D22436
--HG--
extra : source : 5bdf0ad9dc6639dd86499fded67183f77407a8ee
This test ensures that when meta viewport width is fixed, and a viewport
is requested with zero width, the viewport is assigned a height equal to
the scaled display height.
Differential Revision: https://phabricator.services.mozilla.com/D22436
--HG--
extra : moz-landing-system : lando
Cosmin Sabou
Andrea Marchesini
Sylvestre Ledru
Joel Maher
Andrew Swan
Zibi Braniecki
Noemi Erli
Emilio Cobos Álvarez
Ciure Andrei
Ryan Hunt
Andrew McCreight
Rob Wu
Brian Grinstead
Ehsan Akhgari
Narcis Beleuzu
Csoregi Natalia
Edwin Gao
Thomas Wisniewski
Christoph Kerschbaumer
violet
Brad Werth
Mark Banner
sakshaat
Gijs Kruitbosch
shindli