With enabling apz.allow_zooming, both test and reference contents are scaled
down on mobile environments but the scaled size is different because the content
width is different.
Differential Revision: https://phabricator.services.mozilla.com/D138874
With enabling apz.allow_zooming, both test and reference contents are scaled
down on mobile environments but the scaled size is different because the content
width is different.
Differential Revision: https://phabricator.services.mozilla.com/D138874
There are a fair share of desktop mochitests that depend on having
scrollbars take space (and that are useful to test the non-overlay
scrollbar codepath).
Also, GTK overlay scrollbars have opacity animations (they fade out), so
they are much more prone to useless fuzzy intermittent failures.
We get overlay scrollbar testing via Android (Android scrollbars also
don't have animations, which is nice). We seem to disable them for macOS
as well, afaict, just at the system level, so this is consistent with
that.
Differential Revision: https://phabricator.services.mozilla.com/D138507
If a block container has box-decoration-break:clone, its block-end border and
padding (BP) are *usually* drawn at the block-end edge of the current
column/page. Thus, when computing the available block-size for its children, we
should subtract its block-end border BP from it.
When I claim the block-end BP are *usually* drawn at the block-end edge of the
column/page, the exception is when a block container with a definite block-size
runs out of its block-size in a column/page. In this case, the block-end BP is
drawn at the block-end edge of its content-box. This patch wires the effective
content-box block-size computed in nsBlockFrame::Reflow() into
BlockReflowInput's constructor, and we do not subtract its block-end border BP
from the `mContentArea.BSize(wm)` when this case happens.
`BlockReflowInput::ContentBSize()` is the correct available block-size to reflow
the children, precomputed in BlockReflowInput's constructor. See
https://searchfox.org/mozilla-central/rev/c12a59323ee46b29b90c9917a3a7a70ea714ffec/layout/generic/BlockReflowInput.cpp#118-126
The remove hunk was a hack, working only for ColumnSetWrapper with
`box-decoration-break:clone`. It's no longer needed.
Differential Revision: https://phabricator.services.mozilla.com/D138367
The test framework of cross-origin-opener-policy WPTs is based on
broadcast channels to send data across origins. This behavior will fail
when dFPI is enabled because we partition broadcast channels.
This patch disables dFPI for the WPTs that will send data across origins
by using broadcast channels.
Differential Revision: https://phabricator.services.mozilla.com/D138263
This patch adds the --proxy-perftest-page option. With this option, we'll be able to specify which test pages we want to record rather than modifying the pageload_sites.json. Note that the login fields will not be taken into consideration with this option.
You can use the flag as follows (seperate multiple pages with a comma): --proxy-perftest-page microsft,linkedin,netflix
Furthermore, some changes were made to strengthen the conditions around when a login site can be tested (only when RAPTOR_LOGINS is defined locally, or if we are in CI).
Differential Revision: https://phabricator.services.mozilla.com/D137468
Details when calling adb commands are not needed in debug log but
should be available in trace logs. Also logging output when
failures occur should be warnings.
Differential Revision: https://phabricator.services.mozilla.com/D138443
If the instance is not an element and is a child of `Document` or something
non-element node, the method calls `this->AsElement()` in non-element instance.
It should check whether it's an element node or not when there is no editable
parent element.
Differential Revision: https://phabricator.services.mozilla.com/D138230
The timeouts changed to fails since the webauthn token manager uses
GeckoResult directly instead of a callback (change in bug 1753919).
Differential Revision: https://phabricator.services.mozilla.com/D138433
It never returns error since its return type is `void` and it does not take
out param whose type is `ErrorResult`.
Therefore, `ErrorResult` in it is used only for checking whether an error occurs
in the calling methods, but neither `SuppressException()` nor `StealNSResult()`
is called for avoiding assertions at destructing the instance.
For avoiding the assertion, and in this case, it should not use `ErrorResult`.
When the result is completely ignored, `IgnoreErrors()` should be used instead.
Otherwise, when it just needs to know whether an API call failed or not, it
should use `IgnoreErrors` to avoid the redundant calls of `ErrorResult` and
for the performance (`ErrorResult`'s destruction may appear in the profile if
it's used in a hot path).
Differential Revision: https://phabricator.services.mozilla.com/D138231
Paul Adenot
Henrik Skupin
Florian Quèze
Hiroyuki Ikezoe
Marian-Vasile Laza
Julian Descottes
smolnar
Markus Stange
Emilio Cobos Álvarez
Joel Maher
Thomas Wisniewski
Csoregi Natalia
Tim Huang
Cristian Tuns
Kagami Sascha Rosylight
Noemi Erli
Eden Chuang
Ting-Yu Lin
Agi Sferro
Butkovits Atila
David Parks
Alex Finder
Byron Campen [:bwc]
Gregory Mierzwinski
Kash Shampur
Masayuki Nakano
Sebastian Hengst
Glenn Watson