This patch exposes the objectInspector reducer as a regular
file that can be required in the devtools codebase.
This should make things faster to start as we won't need
to load the entire bundle (especially for the inspector where
the reps is only used when navigating to specific subpanels).
This means we need to remove the flow typing for now since
we don't have a cross-toolbox build process like we have
in the debugger.
Differential Revision: https://phabricator.services.mozilla.com/D47728
--HG--
extra : moz-landing-system : lando
This check is wrong when channels are loaded using a proxy.
Bug 1585569 is supposed to fix the issue completely.
Differential Revision: https://phabricator.services.mozilla.com/D47879
--HG--
extra : moz-landing-system : lando
AudioNodeStream is a subclass of MediaStream, which now exposes a
public const mSampleRate member.
Differential Revision: https://phabricator.services.mozilla.com/D47688
--HG--
extra : moz-landing-system : lando
This change mainly removes the `mTracks` member from MediaStream and moves all
associated members up a level, so that a MediaStream in practice represents a
single track.
Classes will be renamed in a future patch to reflect this.
Other changes include:
The new `mEnded` member of MediaStream changes meaning to only become true when
all data in the stream has been processed. It stems from
StreamTracks::Track::mEnded which used to become true as soon as the last bit of
data had been added to a track, and there could still be data in the track that
would get processed in future iterations. We are moving towards not having any
future data in tracks, which is why this change is ok to make -- keeping the old
behavior will soon not make sense.
TrackUnionStream is changed to no longer take a list of streams as input and
forward the union of their tracks to itself. Instead it's limited to having one
track as input at a time.
The autofinishing functionality that TrackUnionStream had before has been
transformed into an autoending functionality to allow it to defer ending until
its been told that it's ok to end through the control API. This lets a single
TrackUnionStream span the lifetime of multiple inputs, which will be useful for
making DecodedStream spec compliant with HTMLMediaElement::CaptureStream(), and
for implementing the currently discussed MediaRecorder::ReplaceTrack(), to name
a few potential use cases.
AudioNodeStreams used to only have a track (and thus an AudioSegment) if the
EXTERNAL_OUTPUT flag was enabled on them. With all MediaStreams now representing
a track, AudioNodeStreams inherently have an AudioSegment as a member. It is
however only used with data if the EXTERNAL_OUTPUT flag is enabled.
Differential Revision: https://phabricator.services.mozilla.com/D45821
--HG--
extra : moz-landing-system : lando
The stream order does not depend on streams' finished state, so these calls are
unnecessary.
Differential Revision: https://phabricator.services.mozilla.com/D47687
--HG--
extra : moz-landing-system : lando
This functionality is not used since we moved to only having a single track per
MediaStream (bug 1493613).
Differential Revision: https://phabricator.services.mozilla.com/D47686
--HG--
extra : moz-landing-system : lando
TrackID has been used to denote tracks that are part of MediaStreams in the
MediaStreamGraph. The TrackInfo::mTrackId IDs are no longer used in the
MediaStream APIs and as such it's not necessary that they have the type TrackID.
This patch changes TrackInfo::mTrackId to be of type uint32_t instead, as that
is the type of Mp4parseTrackInfo::track_id, which is assigned to
TrackInfo::mTrackId as the sole remaining non-static user.
Other users set a static trackId of `1` or `2`, and as such remain supported by
this change.
Differential Revision: https://phabricator.services.mozilla.com/D46763
--HG--
extra : moz-landing-system : lando
The computed value is equivalent to BaselineFrame::frameSize_, but later in the stack
the BaselineFrame::frameSize_ field will be debug-only.
Differential Revision: https://phabricator.services.mozilla.com/D46913
--HG--
extra : moz-landing-system : lando
In addition, make sure the descriptor size stays in sync with the visible rect's size.
The descriptor's size stored in the resource cache is pretty much obsolete now, we should be able to clean it up and remove it.
Differential Revision: https://phabricator.services.mozilla.com/D46803
--HG--
extra : moz-landing-system : lando
serde_yaml has been added to geckodriver, and dependencies
under third_party/rust needs to be updated.
Depends on D44578
Differential Revision: https://phabricator.services.mozilla.com/D47822
--HG--
extra : moz-landing-system : lando
This makes geckodriver configure GeckoView vehicles using a
configuration YAML file. This is the [blessed way to configure such
vehicles](https://mozilla.github.io/geckoview/consumer/docs/automation).
The old way based on intent arguments is kept as long as Fennec
needs to be supported because it doesn't read the configuration file.
And other packages, which are based on GeckoView, will ignore
package specific intent arguments.
The configuration file is always pushed, even when it will be
ignored by the relevant package.
Differential Revision: https://phabricator.services.mozilla.com/D44578
--HG--
extra : moz-landing-system : lando
When clicking native toast on Windows 10, focus moves to another process,
So we have to set focus on Firefox process.
Differential Revision: https://phabricator.services.mozilla.com/D47398
--HG--
extra : moz-landing-system : lando
When user adjusts the video playback rate, which might cause we sending images in a speed that is faster than the speend we composite images.
In this situation, the frame dropping actually won't cause any visual defect and we also don't want to report this frame dropping to user, because it's not caused by system overloading, it's just our compositor doesn't support compositing images in such a high rate.
Therefore, we should check if the dropped images are caused by system overload or high update rate, and only report the former to user.
Differential Revision: https://phabricator.services.mozilla.com/D46236
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Add serialization WPT for CSS comparison functions min/max on <number>
Unfortunately we fail all the test cases because of an existing bug that
we resolve calculated <number> at parse time (crbug.com/1008471).
Nevertheless, the tests are added, and the failured don't block the
launch of min/max.
Bug: 978682, 1008471
Change-Id: Ia402dbeb5ca7bd52eab8df83e3d52a4511647c6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827826
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700616}
--
wpt-commits: 07c52e79870a5c7cf7aa37a7bc2c3e232b295d03
wpt-pr: 19334
