These tests used <iframe mozbrowser> for convenience, mostly forcing
themselves to only run in non-e10s mode in the process, but none of them
really have any need to.
Differential Revision: https://phabricator.services.mozilla.com/D70745
These were added for the sake of app browsers, and all of the code which
actually needed them has since been removed.
Differential Revision: https://phabricator.services.mozilla.com/D70741
It makes no sense that the first thing in the session would be considered as
wrapping, it was happening only because we were incorrectly failing to find a
"visible" range deep in Gecko (so we started back from the beginning of the
document, wrapping).
Differential Revision: https://phabricator.services.mozilla.com/D71157
Multiple issues here. The IsRangeVisible code was wrong, it was returning false
for ranges that were perfectly valid, but outside the viewport, because the
following piece of code:
if (!aMustBeInViewPort) {
// This is an early exit case because we don't care that that range
// is out of viewport, so we return that the range is "visible".
return true;
}
Was incorrectly after some stuff checking viewport visibility. This code is
pretty complex for no good reason, it wants to do something very
simple: Start from the visible selection if possible.
This patch still achieves this, using IsRangeRendered (which does a proper
hit-test to figure out if a range is in the viewport). Should have no behavior
differences except for non-collapsed ranges that are partially inside the
viewport.
Differential Revision: https://phabricator.services.mozilla.com/D71067
This also fixes a bug where we weren't recording the telemetry probe clicks on breached password learn more links due to the refactoring and renaming of the .alert-link class. A test has been added that would have caught that mistake in automation.
Differential Revision: https://phabricator.services.mozilla.com/D70142
This also fixes a bug where we weren't recording the telemetry probe clicks on breached password learn more links due to the refactoring and renaming of the .alert-link class. A test has been added that would have caught that mistake in automation.
Differential Revision: https://phabricator.services.mozilla.com/D70142
Currently, we build android emulator packages manually and upload to
tooltool.
This patch switches it to be pulled from the toolchain built artifacts.
This also allows android tests to run in the staging environment.
Differential Revision: https://phabricator.services.mozilla.com/D68617
The Bookmark page button ignores activation if there is pending update. Thus,
the test must wait for the update to be finished before synthesizing mouse
actions.
Differential Revision: https://phabricator.services.mozilla.com/D71114
The Bookmark page button ignores activation if there is pending update. Thus,
the test must wait for the update to be finished before synthesizing mouse
actions.
Differential Revision: https://phabricator.services.mozilla.com/D71114
1. Fixed "warning: use 'using' instead of 'typedef'" for OrderState.
2. Removed `FlexItem* item` to fix the "warning: Value stored to 'item'
is never read".
Differential Revision: https://phabricator.services.mozilla.com/D69486
These reftests are copied from flexbox-unbreakable-child-1-*.html and
flexbox-unbreakable-child-1-*-wrap.html with "box-decoration-break:
clone" added to the flex container.
Note that flexbox-unbreakable-child-3-ref.html is redesigned. It is not
copied from flexbox-unbreakable-child-1-ref.html with
"box-decoration-break: clone" added because the bottom border doesn't
show up in sub-test 3 & 4. (bug 1564726 perhaps?)
Differential Revision: https://phabricator.services.mozilla.com/D69475
By passing unconstrained aAvailableBSizeForContent to DoFlexLayout, we
can get the flex container's desired content-box size as if there's no
pagination. We could then use this content-box size and
maxBlockEndEdgeOfChildren to rewrite the logic to determine flex
container's final size.
I still maintain the compatibility with block frame that if the flex
container is running out of block-size, it can still become incomplete
and request an zero block-size continuation. One comment in block frame
feels this is wrong, but fixing it is not in the scope of this bug.
https://searchfox.org/mozilla-central/rev/4ccefc3181f9d237ef4ca8bd17b4e7c101ddf7b5/layout/generic/nsBlockFrame.cpp#7715-7718
Differential Revision: https://phabricator.services.mozilla.com/D69474
We want mContentBoxMainSize and mContentBoxCrossSize in SharedFlexData
to be the final content-box without regards to pagination, but it is not
correct yet. A later part will pass NS_UNCONSTRAINEDSIZE as
availableBSizeForContent so that DoFlexLayout can calculate the correct
size.
Differential Revision: https://phabricator.services.mozilla.com/D69472
Jan-Ivar Bruaroey
Dzmitry Malyshau
Andreea Pavel
Jeff Muizelaar
Shane Caraveo
Ciure Andrei
Kris Maglione
Emilio Cobos Álvarez
Jared Wein
Daosheng Mu
Imanol Fernandez
Erik Nordin
Scott
Bogdan Tara
Nicolas Silva
William Durand
Wander Lairson Costa
Edgar Chen
Ting-Yu Lin