Annoyingly, setting the pref doesn't magically make the function appear on the
current window, so we create an iframe and retrieve it from there.
MozReview-Commit-ID: 9fOr4YJOzXh
--HG--
extra : rebase_source : d23643b388538955cc831a3b6e1473232ab5498a
The browser-chrome test suite now detects and reports unhandled rejections of native Promises, in addition to those created by Promise.jsm. The whitelisting mechanism is updated to use primarily the PromiseTestUtils.expectUncaughtRejection function. Tests will fail if a rejection that is not whitelisted occurs, or if a whitelisted rejection does not occur anymore.
MozReview-Commit-ID: 1beGB5GG8Ty
--HG--
extra : rebase_source : b6573f8e2001f91d0e5a50f6376b191459549e94
extra : intermediate-source : 0411e687044ecc7b56684196238e6e6e68a9d685
extra : source : 8d53be05afc59519c5ce8cfae96d284a972fda71
We test the expected behavior base on the pref,
"security.data_uri.unique_opaque_origin".
We run the legacy test when the pref is off, however if the pref is on,
we run the new behavior, loading an iframe with X-FRAME-OPTIONS in a
data: URI should be blocked.
A mochitest browser test for image blocking.
We query the blocking status by reading imageBlockingStatus.
See nsImageLoadingContent.cpp for the logic of blocking image.
In this test we verified the following behavior:
1. image is loaded.
2. image is blocked.
3. mCurrentRequest doesn't have size yet, so it should be replaced.
4. mCurrentRequest already got size, the following request should be a
pendingRequest.
There are several places in the WebExtensions framework where we currently
need to repeatedly serialize and deserialize structured clone data as it
passes through message managers, which can lead to significant performance
issues.
This helper class lets us serialize a value directly from the source extension
context into an opaque blob, and then directly deserialize it into the target
context on the other end, with no X-ray overhead or clones into privileged
scopes in-between.
MozReview-Commit-ID: 4QzHi89onxc
--HG--
extra : rebase_source : 2ec196ca9ce9be90b7eadf136c938373ac7d3fdd
This patch prevents a part of the test from creating a notify-focus event at random times later in the test by taking care of it as soon as it can be received. It also removes an unecessary focus call.
MozReview-Commit-ID: DJJaKmaT5wm
--HG--
extra : rebase_source : 1ea997d75657a8f8394b0d708b36d9773a683f6e
The browser-chrome test suite now detects and reports unhandled rejections of native Promises, in addition to those created by Promise.jsm. The whitelisting mechanism is updated to use primarily the PromiseTestUtils.expectUncaughtRejection function. Tests will fail if a rejection that is not whitelisted occurs, or if a whitelisted rejection does not occur anymore.
MozReview-Commit-ID: 1beGB5GG8Ty
--HG--
extra : rebase_source : 64395c5fdf25deebd60dfbf2cf5df3cbf7ca8abb
extra : amend_source : 0a3f13419c050662680f2bd110d724b3bf991732
extra : source : 8d53be05afc59519c5ce8cfae96d284a972fda71
The browser-chrome test suite now detects and reports unhandled rejections of native Promises, in addition to those created by Promise.jsm. The whitelisting mechanism is updated to use primarily the PromiseTestUtils.expectUncaughtRejection function. Tests will fail if a rejection that is not whitelisted occurs, or if a whitelisted rejection does not occur anymore.
MozReview-Commit-ID: 1beGB5GG8Ty
--HG--
extra : rebase_source : 59e5b84cb431f3ca28287d30a3da8fbea1363ec5
The previous version of this test assumed that it was in control of all
processes (except for a single one that was hanging around). That meant that
changes to the environment, such as running it on a different branch could
cause it to fail. Now we explicitly test that creating new tabs creates a new
content process (and that the final tab creation *doesn't* do so) with a
sanity check that new ContentParents don't reuse the same underlying OS
process. Because we're now explicitly testing what we want, this works whether
the current branch holds a random extra process alive or not.
MozReview-Commit-ID: CNgLGL32Iog
--HG--
extra : rebase_source : f27d132d00bdd94d7034cc63c83bbacfe04bde0c
According to the source map spec, the X-SourceMap header is deprecated
in favor of SourceMap. This adds support for the newer name. The test
case is a copy of the X-SourceMap test with the obvious change.
MozReview-Commit-ID: 8J6YN8xMIfb
--HG--
extra : rebase_source : 76673c096f5571065527073575b6e8c033ae68be
This uses XPCOM to replace the default process selector with one that always
asks for a new process and then put the old one back again. This comes with a
test to prove that it works.
MozReview-Commit-ID: Bq6KP4VzP7W
--HG--
extra : rebase_source : a42662d67f7eeca8bc5870d3c70c086abf582164
Perhaps, test_nsITextInputProcessor.xul is copied from another file and I failed to remove unnecessary code. That might cause stealing focus from child window and preventing to run waitForFocus().
MozReview-Commit-ID: 5Sym3mcauH7
--HG--
extra : rebase_source : 9a9118f29b64f223935d1199645425a75a936daf
Since there are some mechanism to prevent from loading multiplace resorce at a
same time for an element, I rewrote the test to isolate each subtests and make
sure they will not bother each other.
MozReview-Commit-ID: 59h8rzjDxKj
--HG--
extra : rebase_source : 8ab8167080a69decf2e1d3c0c74a5f96bef5ecec
Create a test to guarantee current behaviors. We should only set urgent-start
when it is triggered by user input events rather the other events or no any
events.
MozReview-Commit-ID: 1ehiD3ua5Kl
MozReview-Commit-ID: H6bL8PpzijJ
--HG--
extra : rebase_source : ae66b05eded40907d690ac69ea37a739413b9e51
Wes Kocher
Nathan Froyd
Blake Kaplan
Tobias Schneider
Sebastian Hengst
Ben Kelly
Beekill95
Paolo Amadini
Yoshi Huang
Henri Sivonen
Boris Zbarsky
Nicolas B. Pierron
Kris Maglione
Joel Maher
Carsten "Tomcat" Book
Greg Mierzwinski
Andrea Marchesini
Ryan VanderMeulen
Mats Palmgren
btian
Tom Tromey
Masayuki Nakano
Christoph Kerschbaumer
Tom Tung