On the compositor we store animation values in a hash table and the hash is
the compositor animation id which is a unique id for each property respectively.
So we can get the corresponding animation value for the given property.
In this patch there are lots of duplicated code, but they will be removed in the
next patch.
MozReview-Commit-ID: 7EboVcculcg
--HG--
extra : rebase_source : 304ea80849af8af72a07437736041aeabbe47eeb
Re-enable the test that was disabled in bug 1381305 and fix the
underlying issue that caused th intermittent failure in the first place.
MozReview-Commit-ID: BL9wS2fogaf
--HG--
extra : rebase_source : 685f43b2e47d80f71814385a5c8b94fd3000eac9
Particularly in CAD applications, it's common to call drawElements many times on small
ranges of indices. This causes our naive maxVertId range cache to degenerate.
In most cases, the index buffer won't actually contain any indices outside the associated
VAO buffers' ranges. We should test first against this global upper-bound, only testing
for an exact maxVertId for the subrange if the upper-bound test fails.
Differential Revision: https://phabricator.services.mozilla.com/D2488
--HG--
extra : moz-landing-system : lando
Fairly straightforward. This should allow us to enable our
forcepaint telemetry again without an added cost, since it's
just piggybacking on the existing content process BHR.
MozReview-Commit-ID: 83l9xnPfc9u
--HG--
extra : rebase_source : d53f1e9adfff1d9bf3610be634f9ece08a2ec154
Renamed the pref media.webrtc.rsdparsa_enabled to media.peerconnection.sdp.rust.compare
Added the pref media.peerconnection.sdp.rust.enabled
Added both to all.js
media.peerconnection.sdp.rust.compare: Controls whether the parsing result comparer for sipcc and rsdparsa runs or not.
media.peerconnection.sdp.rust.enabled: Controls whether the rsdparsa runs in parallel to the sipcc parser.
MozReview-Commit-ID: Ac5P7T2NBYD
--HG--
extra : rebase_source : afd60243ccba27965bea193bbe29d91bf7bf2644
This should hopefully prevent races where we run promise handlers during
worker shutdown, when we're canceling regular events anyway.
Differential Revision: https://phabricator.services.mozilla.com/D2376
--HG--
extra : moz-landing-system : lando
Created a new parcelable which is sent to MediaControlService where
the notification is created based on the data of this object instead of
referencing a static notification. Toggling the service is now done through
startService with a specific action for shutting down instead of calling
stopService due to concurrency issues where the service can be stopped before
having a chance to call startForeground.
MozReview-Commit-ID: 6qNPintkVy
--HG--
extra : rebase_source : b161d07e8fb0831deb7b4549985e6b5c276366c0
The input expansion tests are removed since the new test now cover the input
growing/shrinking.
MozReview-Commit-ID: 4RIQar4ytX
--HG--
extra : rebase_source : 0372ef695c37646cabc7f40ec22e3c652dcce133
extra : source : f4aef5b3c68fca33e19dcf67e1b7e5fc4006a227
Make sure the window XID is propagated to X server, we can fail otherwise
in GPU process.
MozReview-Commit-ID: BMkLvhs4vRt
--HG--
extra : rebase_source : 34269cbf7e088fd15c090f3abc8ee2d46da307c4
This new id is added in the PerformanceInfo data and helps consumers distinguish
counters.
MozReview-Commit-ID: 7kEmqJcVggM
--HG--
extra : rebase_source : 40cca4c937f846db93ec1315036ad1bac04bc762
Automatic update from web-platform-testsUpdate mozinstall from 1.15 to 1.16.0 (#11627)
--
wpt-commits: b305e43f8a9d2a94931d673d90606c1d01d1231f
wpt-pr: 11627
Automatic update from web-platform-testsUpdate certs for hosts changes.
This is required to use the recently added hosts over https.
--
wpt-commits: f2f1b207292a20677b185b828f00a8894188a27d
wpt-pr: 12108
Automatic update from web-platform-testsAdding tests against and fixes for tabs in Server-Timing headers
According to the spec
(https://w3c.github.io/server-timing/#the-server-timing-header-field),
optional whitespace is allowed amongst parameter names and values. We
should be discarding this whitespace during parsing but, when there are
tabs, we were treating it like an error and discarding the whole value.
Changed the code that tokenizes HTTP headers to skip tabs and spaces
when consuming optional whitespace.
BUG=798446
Change-Id: If776761e5ea199e662ec7b2b5aa245e4581131fd
Reviewed-on: https://chromium-review.googlesource.com/1147258
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Tom McKee <tommckee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#577325}
--
wpt-commits: 4ec913040882c7bb28846a65e7e086785dcf2ab6
wpt-pr: 12149
Automatic update from web-platform-tests[infra] Revert recent reversion to config file
This reverts commit 9f21134354f7d02f1497826d00ba4297ba78c445.
The initial reversion was motivated by an integration issue with the
TaskCluster service. The underlying bug has been corrected [1] making
this changeset suitable for `master`.
[1] https://github.com/taskcluster/taskcluster-github/pull/265
--
wpt-commits: e62afac4c9dac57d8b81d2bf1364694e3d653ff9
wpt-pr: 12151