In addition to updating gfx/webrender and gfx/webrender_traits, this updates
gfx/webrender_bindings for:
- API changes to update_image and push_stacking_context.
- Version bumps needed in Cargo.toml
Also, since offscreen_gl_context is no longer a dependency, this patch removes
that crate and various other crates it depends on.
This patch makes the size of inner windows will be automatically rounded for
either window.open() with window features or setting window size through
innerWidth/Height and outerWidth/Height when fingerprinting resistance is
enabled. If the given value is greater the maximum available rounded size, then
it will be set to the maximum value. Otherwise, the size will be set to the
nearest upper 200x100.
This patch also adds one helper function in nsContentUtils for calculating the
rounded window dimensions.
MozReview-Commit-ID: J2r3951vuNN
--HG--
extra : rebase_source : a44b19bdf2ce7e90fc831ddc2b85a86d594cb0c3
This patch fixes two related issues.
1. The AutoStopwatch uses a stack-allocated `mozilla::Vector` to
communicate with its callback during each compartment switch. This
vector was designed to allow its contents to be stack-allocated but
they turned out to be accidentally heap-allocated.
2. During each tick, the stopwatch fills a vector
`recentGroups_`. This vector always started with minimal capacity and
had to grow repeatedly as groups were added, causing repeated
reallocations. This patch preallocates `recentGroups_` to have the
same capacity as the previous tick. We expect that this should
eventually reach a stable size that closely matches the actual needs
of the process.
MozReview-Commit-ID: A7e3HNdSuML
--HG--
extra : rebase_source : bb205970b4186d9325dded7ddae066bcad18fb0e
CLOSED TREE
Backed out changeset 4ac559eea9ec (bug 1348803)
Backed out changeset 2ab6e0b8aec6 (bug 1348803)
Backed out changeset f966aef934b1 (bug 1348803)
We could register media control related event after the tab has active media.
But we still need to register "audioFocusChange" in the beginning, because it
affect every tab even the tab has no active media.
MozReview-Commit-ID: 4pBKIR8F5tV
--HG--
extra : rebase_source : fc26c98ed7b33552b4eba5b20168394b1b1a4390
Also, avoid two entirely unused imports.
This avoids loading the various osfile jsms at startup.
The additional shim method for sysinfo is needed in
test_TelemetryEnvironment.js because delaying the intialization of
osfile results in loading osfile_shared_allthreads.jsm after the shim
sysinfo has been added, which initializes
Ci.nsIOSFileConstantsService, which calls into sysinfo in
InitOSFileConstants().
MozReview-Commit-ID: D7IWk20TRt1
--HG--
extra : rebase_source : cf820b1ed72a78ff34e99d2129401c4806a68175
There are two sets of three probes here.
The first set of probes reports the maximum contiguous frames dropped during
compositor animations. This gives us some idea of the volatility of the
compositor framerate.
The second set of probes reports the frame throughput, which is the number of
actual frames composited divided by the expected number of frames (based on the
vsync interval and wall-clock time) during compositor animations. The ratio is
scaled up to 1000, so values of 1000 should indicate a "perfect score". The
probes use linear bucketing with a max value of 1500 in case we get abnormal
cases where we composite more frames than expected.
Within each set, there is one probe for compositor animations triggered by the
chrome process, one for compositor animations triggered by a content process,
and one for compositor animations driven by APZ.
MozReview-Commit-ID: LFJsEPnQhja
--HG--
extra : rebase_source : d943b4612c2a84b0d4b85c5eafb0d0025ffba80f
We used to have this rule in shared stylesheet for both mobile and
desktop, but the namespace mismatched after visual refresh (De-XUL).
Now we should add this rule back to hide cursor while fading out.
MozReview-Commit-ID: HDZKn8CrQ5X
--HG--
extra : rebase_source : 7a63650b9f048dd5b0b0b79ce289bc762cc6a07b
To improve build times, we've decided to only build libxul-gtest when
it's specifically requested, i.e. via `mach gtest` or similar. However,
our build setup specifies that gkrust-gtest, the Rust code specifically
for libxul-gtest, is built during normal builds. This library takes a
significant amount of time to compile and is generally not needed.
This patch changes the gkrust-gtest library to only be visible under the
same conditions that libxul-gtest is built, thus speeding up normal
builds.
Enable safebrowsing v4 completion but ignore the result by checking preference in
nsUrlClassifierLookupCallback::Completion may cause telemetry measure incorrect match
result since v4 completions will always be ignored.
So in this patch we move the preference check after telemetry is measured and then we
ignore the result.
MozReview-Commit-ID: J29JitvW3Lc
--HG--
extra : rebase_source : 0cf8797de476980ce25d83099e6526321308327c
This changeset changes tests using ForgetAboutSite.removeDataFromDomain
to yield on it, since now it is a Task
MozReview-Commit-ID: 72OEYoO1avd
--HG--
extra : rebase_source : 9ea8cc06493c3e965d260dc9377461ff29fe572a
Amended to fix review changes
(stylistic + other)
Turns all cleaners into promises so they run asyc
MozReview-Commit-ID: DV5ug6vNXkS
--HG--
extra : rebase_source : df9d9cd98f25e2a899c0a74f836f217d3ad52426
Currently we hand over a crash ping to the pingsender via a pipe; if the
pingsender fails to send the ping we rely on the CrashManager assembling and
sending one instead. Since the crashmanager is not aware of whether the ping
was sent or not this causes duplication on the server side. To solve this
problem we save the ping to disk instead, read it from the pingsender and
delete the file only if the ping was sent. In this scenario the CrashManager
will know that a ping was already sent and will not send a new one.
This patch removes all the code used to deal with pipes between the telemetry,
crashreporter and pingsender code and also tries to cut down the amount of
platform-specific code we have in this machinery.
MozReview-Commit-ID: ASm2jnDagCK
--HG--
extra : rebase_source : 9091d7897d17dad68e05e945e777e42998d020d0
Add new tests and move some share codes to head.js.
MozReview-Commit-ID: GcCio6JupZu
--HG--
extra : rebase_source : a9324aaebd89412d77bed19b0554e6cf2959b6e2
The probes keep track of V2 and V4 server response to update and getHash
request. The probes are keyed by provider
MozReview-Commit-ID: 3Uxjm6H77lE
--HG--
extra : rebase_source : 647523a24bad8334dbb34758954a5f5db0e9b96c
