Rerunning via action (i.e. from treeherder) currently fails for partials, as the
task isn't in the full task graph (since the parameters for the push-task don't
have the partials). Since (at least currently) all tasks not in the full graph
are release tasks, assume that they require reruns, not retriggers, to allow easier
handling of tasks via treeherder.
Differential Revision: https://phabricator.services.mozilla.com/D56516
--HG--
extra : moz-landing-system : lando
Changes:
Replace the `execfile` call with a cross-compatible version of the call.
Differential Revision: https://phabricator.services.mozilla.com/D57039
--HG--
extra : moz-landing-system : lando
Changes:
In python3, the `dictionary.keys()` call no longer returns a list, but a view. The test requires that the output be sortable, so wrap it in a `list()` call to ensure sortability.
Differential Revision: https://phabricator.services.mozilla.com/D57045
--HG--
extra : moz-landing-system : lando
It calls `Document::FlushPendingNotification()` so that we should mark it
as `MOZ_CAN_RUN_SCRIPT`.
And the method calls it of `mDocument` and `mDocument` is never modified
after it's initialized. Therefore, we can move the initializer to the
constructor and make `RefPtr<Document>` to `RefPtr<Document> const`. Thus,
we can avoid unnecessary auto `RefPtr`.
Differential Revision: https://phabricator.services.mozilla.com/D55803
--HG--
extra : moz-landing-system : lando
Debugger::generatorFrames and Debugger::frames used to have looser types, and
the code working with them needed to downcast in order to work with more
specific object types. But now the key and value types in those maps are
well-typed, so the downcasts do nothing and can be removed.
Depends on D56837
Differential Revision: https://phabricator.services.mozilla.com/D56838
--HG--
extra : moz-landing-system : lando
Responsibility for creating entries in Debugger::generatorFrames was moved to
DebuggerFrame::setGenerator, so Debugger::getFrame is only doing lookups now,
and can use the more restricted `Ptr` type for the results of its lookups.
Depends on D56836
Differential Revision: https://phabricator.services.mozilla.com/D56837
--HG--
extra : moz-landing-system : lando
Subsequent patches introduce Debugger.Object.prototype.promiseReactions, which
will be the first case in which we've ever needed to create a Debugger.Frame for
a suspended generator call. All prior generator support creates Debugger.Frames
only for frames on the stack.
This patch changes DebuggerFrame::create to take both a FrameIter and a
generator object, both optional (one or the other must be present), and create a
frame with whatever data is provided. The sole caller is adjusted accordingly.
Depends on D56835
Differential Revision: https://phabricator.services.mozilla.com/D56836
--HG--
extra : moz-landing-system : lando
SpiderMonkey Promises use a hybrid representation for the list of reaction
records attached to a promise: an empty list is `undefined`; a list of one
element is the reaction record itself, and a list of two or more records is an
array.
TriggerPromiseReactions and PromiseObject::dependentPromises duplicate the code
for walking over a reaction record list. Later patches in the series will
introduce a third function that does it, so it seemed like a good time to
abstract out the iteration.
This patch defines the function 'ForEachReaction', which applies a closure to
each reaction in the list, and changes existing code to use it.
Differential Revision: https://phabricator.services.mozilla.com/D56835
--HG--
extra : moz-landing-system : lando
Since bug 1514429 window.inner{Width,Height} don't return the visual viewport
size so once after the content scale changed, i.e. the visual viewport size
doesn't match window inner size, GeckoView::ScrollBy and ScrollTo don't work
as expected. This commit has JUnit tests to generate the situation by calling
nsIDOMWindowUtils.setResolutionAndScaleTo.
Differential Revision: https://phabricator.services.mozilla.com/D56321
--HG--
extra : moz-landing-system : lando
`MediaControlKeysEvent` should represent possible control key events, so adding a non-existing `eNone` in this class is not good.
Differential Revision: https://phabricator.services.mozilla.com/D57022
--HG--
extra : moz-landing-system : lando
There are multiple seeking states in `MDSM`, it would be good to see the full name of the seeking state on the debug log to know what seeking state we're using.
Differential Revision: https://phabricator.services.mozilla.com/D56823
--HG--
extra : moz-landing-system : lando
Rather than applying the volume change to the DecodedStream, which won't be
played until the buffer catches up, instead apply the volume to the segments
as they are consumed by the MediaTrackGraph.
Differential Revision: https://phabricator.services.mozilla.com/D56276
--HG--
extra : moz-landing-system : lando
These events were sent excessively on onStateChange. This patch makes it so that:
- we only listen to top-level document changes (we used to send all events from iframes)
- we don't send events unless there's tracking content on the page
- we only send a single event on tab switch instead of multiple
Differential Revision: https://phabricator.services.mozilla.com/D57006
--HG--
extra : moz-landing-system : lando
When launched from a browser we can retrieve a site manifest to provide more
information about the site.
Differential Revision: https://phabricator.services.mozilla.com/D56287
--HG--
extra : moz-landing-system : lando
FeatureState does not add a log when it is enabled by default. But we want it for Feature::WEBRENDER_COMPOSITOR.
Differential Revision: https://phabricator.services.mozilla.com/D56848
--HG--
extra : moz-landing-system : lando
Any number of outer windows may be attached to a BrowsingContext over its
lifetime. While the BrowsingContext is alive, it's easy to keep track of which
of these is active, and therefore which of its inner windows is active. After
it has been discarded, though, it discards its docShell reference, so all we
can tell about an inner window is whether it is active for its own outer
window, but not whether it should be considered active for its
BrowsingContext.
This patch updates the BrowsingContext detach logic to store a flag on the
current inner window recording that it was active when its BrowsingContext was
detached, and then later checks that flag to determine if it is the current
window for a detached BrowsingContext.
Differential Revision: https://phabricator.services.mozilla.com/D49032
--HG--
extra : moz-landing-system : lando