We need to setup a case where the visual viewport is smaller than the layout
viewport. Faking a pinch zoom through touch events is imprecise, whereas calling
windowUtils.setResolutionAndScaleTo(value > 1) to simulate the equivalent
effect of a pinch-zoom on the page led to the subsequent scroll attempt failing
quite often even after calling waitForApzFlushedRepaints().
So instead, we set up a very wide layout viewport through the meta viewport tag,
which on Desktop means additionally enabling the dom.meta-viewport.enabled pref.
Differential Revision: https://phabricator.services.mozilla.com/D15791
--HG--
extra : moz-landing-system : lando
We only ever add a single sheet (EditorOverride.css) there anyway.
Depends on D16282
Differential Revision: https://phabricator.services.mozilla.com/D16283
--HG--
extra : moz-landing-system : lando
Add wpt for testing interpolation result on grid-template-{columns|rows}.
Depends on D16129
Differential Revision: https://phabricator.services.mozilla.com/D16130
--HG--
extra : moz-landing-system : lando
Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1348519#c6 and
https://github.com/w3c/csswg-drafts/issues/3201:
Currently grid-template-rows/columns interpolate “per computed value”, which
means that if the number of tracks differs, or any track changes to/from a
particular keyword value to any other value, or if a line name is added/removed
at any position, the entire track listing is interpolated as “discrete”.
But we "agree" with two more granular options:
1. Check interpolation type per track, rather than for the entire list, before
falling back to discrete. I.e. a length-percentage track can animate between
two values while an adjacent auto track flips discretely to min-content.
2. Allow discrete interpolation of line name changes independently of track
sizes.
Besides, for the repeat() function, it's complicated to support interpolation
between different repeat types (i.e. auto-fill, auto-fit) and different repeat
counts, so we always fall-back to discrete if the first parameter of repeat()
is different.
Depends on D16339
Differential Revision: https://phabricator.services.mozilla.com/D16129
--HG--
extra : moz-landing-system : lando
These tests mostly use either the debugger (requires separate compartemnts for
debugger/debuggee) or require a new compartment for things like nukeAllCCWs().
Differential Revision: https://phabricator.services.mozilla.com/D16172
--HG--
extra : moz-landing-system : lando
I added this optimization in bug 1299107 to share more shapes across
compartments. Unfortunately this doesn't play well with same-compartment
realms (ICs can misbehave) because it relies on compartments being isolated
from each other.
I think we should remove this optimization:
* Fixing the IC issue is impossible without deoptimizing everything.
* I added it mainly for chrome globals. The shared-JSM-global work has eliminated
the need for this there.
* Same-compartment realms win memory back by eliminating CCWs etc.
* It's quite a lot of complicated code.
Differential Revision: https://phabricator.services.mozilla.com/D16170
--HG--
extra : moz-landing-system : lando
We want to use this shell flag in automation. Some globals really need their
own compartment so tests can use newGlobal({newCompartment: true}) to opt-out.
Differential Revision: https://phabricator.services.mozilla.com/D16166
--HG--
extra : moz-landing-system : lando
This fixes an issue from bug 1518586.
It stemmed from the fact that I misunderstood how the 'parser' attribute
was being used in mach commands and didn't do enough testing. This patch
fixes things such that we check that 'parser' is not None, as well as
add the completion targets from 'handler.arguments'.
Differential Revision: https://phabricator.services.mozilla.com/D16501
--HG--
extra : moz-landing-system : lando
I think it's a little bizarre for this to be part of the standard, but if it
weren't there, I wouldn't know it was safe to do this.
Differential Revision: https://phabricator.services.mozilla.com/D14511
--HG--
extra : moz-landing-system : lando
Bug 1464869 resulted in blank lines being inserted between comments
and the classes they describe in the gdb unwinder code. This patch
changes most of these comments into doc strings instead.
MozReview-Commit-ID: 6XQwheUNRxI
Differential Revision: https://phabricator.services.mozilla.com/D7174
--HG--
extra : moz-landing-system : lando
This prevents mouse events from firing on browsers in unfocused windows. It used to be done
with the [clickthrough=never] attribute set from XBL content.
Differential Revision: https://phabricator.services.mozilla.com/D16498
--HG--
extra : moz-landing-system : lando
No change in behavior that I'm aware of. It should be correct either way,
since the object is guaranteed to be an object created just so by code
elsewhere in the Streams implementation. But the intended purpose of
GetPropertyPure is in a fast path, backstopped by an actual GetProperty, not
for cases like this.
Differential Revision: https://phabricator.services.mozilla.com/D14505
--HG--
extra : moz-landing-system : lando
Bobby Holley
Jan Henning
Julien Wajsberg
Ryan VanderMeulen
Gurzau Raul
Csoregi Natalia
Narcis Beleuzu
Cameron McCormack
Kris Maglione
Boris Chiou
Michael Froman
Jorg K
Noemi Erli
Florens Verschelde
Jan de Mooij
Iain Ireland
Andrew Halberstadt
Jason Orendorff
Tom Tromey
Brian Grinstead
Emilio Cobos Álvarez