It would cause an assertion failure when OutputStreamManager was released on
main thread. It could be wrapped in an nsMainThreadPtrHandle instead, but that's
exactly what mPrincipalHandle is, so we can use that for both needs.
Differential Revision: https://phabricator.services.mozilla.com/D40789
--HG--
extra : moz-landing-system : lando
1. ShmemPool.cpp is now built for --disable-webrtc builds.
2. ShmemPool no longer uses the gCamerasParentLog logger, it
uses its own logger.
3. ShmemPool log macros were updated with a SHMEMPOOL_ prefix
to avoid undef-ing other log macros.
Differential Revision: https://phabricator.services.mozilla.com/D40722
--HG--
extra : moz-landing-system : lando
Combine the LazyScript::function_ and JSScript::global_ fields into the
BaseScript type. This provides a common definition of script realm and
compartment. Currently a non-lazy function script will set this to point
this to the global, but in future it should be made to point to
canonical function for both the lazy and non-lazy cases.
Differential Revision: https://phabricator.services.mozilla.com/D40520
--HG--
extra : moz-landing-system : lando
The realm can be read off the global object and we can remove one step
in the mergeRealms code.
Differential Revision: https://phabricator.services.mozilla.com/D40519
--HG--
extra : moz-landing-system : lando
- This patch makes sure that we don't create nsDNSService on both child process and middleman process.
- gNeckoChild won't be created in middleman process, so it's fine to create ChildDNSService on middleman process.
- Add some MOZ_DIAGNOSTIC_ASSERT in TRR, so we know where TRR is used on child process.
Differential Revision: https://phabricator.services.mozilla.com/D40018
--HG--
extra : moz-landing-system : lando
The mouse should not be hovering the results pane, or it may change the
aspect of a result.
Differential Revision: https://phabricator.services.mozilla.com/D40658
--HG--
extra : moz-landing-system : lando
Create an event in MediaFormatReader the will signal to the HTMLMediaElement to initiate a new storing according to the latest VideoInfo. Also when the application is shutting down, trigger a new storing early enough, before all the events are disconnected.
Differential Revision: https://phabricator.services.mozilla.com/D38316
--HG--
extra : moz-landing-system : lando
Make use of the new DecoderBenchmark class in MediaCapabilities instead of the old Benchmark mechanism.
Differential Revision: https://phabricator.services.mozilla.com/D38315
--HG--
extra : moz-landing-system : lando
Create a class that gets the video properties and the frame statistics, calculates the score in percentage for that video playback, creates a key string according to video properties and trigger the storage of the score.
The video properties used are the resolution, the frame rate and the bitdepth.
For the key, a range of levels has been created for each property and the video is categorised on the closest levels. The key consists of the various levels like: "ResolutionLevel5-FrameRateLevel1-8bit".
Finaly, it uses the IPDL protocol to store the pair of the score and the key.
Differential Revision: https://phabricator.services.mozilla.com/D38314
--HG--
extra : moz-landing-system : lando
The database is accessible from the parent process due to to the sandbox thus it is required an IPDL protocol that will transfer the queries and the results
Differential Revision: https://phabricator.services.mozilla.com/D38313
--HG--
extra : moz-landing-system : lando
We are unsure as to the actual cause of the crash, but we suspect that when fullscreen exists,
the even listener is not being called. That was leaving `mFullscreenListener` alive when the DTOR gets called
hitting the `MOZ_ASSERT(!mFullscreenListener)`.
We now always all call UnlockDeviceOrientation() in the DTOR to ensure that:
1. `hal::UnlockScreenOrientation()` gets called.
2. `mFullscreenListener` gets null'ed
3. we `RemoveSystemEventListener()` for "fullscreenchange".
Differential Revision: https://phabricator.services.mozilla.com/D40743
--HG--
extra : moz-landing-system : lando
This patch adds two more checks for the icon state in the current TP
switch flow test.
Differential Revision: https://phabricator.services.mozilla.com/D40177
--HG--
extra : moz-landing-system : lando
This patch makes the blue dot to be shown when the tracking protection
is disabled. And this updates the style of the blue dot on the TP switch
to match the spec.
Differential Revision: https://phabricator.services.mozilla.com/D40175
--HG--
extra : moz-landing-system : lando
This patch makes the blue dot in the TP switch section to be related to
the 'enabled' attribute of the TP switch section.
Differential Revision: https://phabricator.services.mozilla.com/D40174
--HG--
extra : moz-landing-system : lando
This patch adds a blue dot indicator on top of the tracking protection
icon if the tracking protection is disabled for the given site.
Differential Revision: https://phabricator.services.mozilla.com/D40173
--HG--
extra : moz-landing-system : lando
We check surrogate pair at specific index in `nsTextFragement` in a lot of
places. This requires boundary check of the index so that it can cause
security issue and crash reason with simple mistake, and also it steals
your time to understand the code what it does especially when it's a
part of an `if` condition.
Therefore, this patch adds new API to `nsTextFragment` and makes the all
surrogate pair handlers of `nsTextFragument` use new API.
Differential Revision: https://phabricator.services.mozilla.com/D39689
--HG--
extra : moz-landing-system : lando
The current test doesn't actually do anything because divs with IDs are
always created.
Differential Revision: https://phabricator.services.mozilla.com/D40674
--HG--
extra : moz-landing-system : lando
Previously, if a hidden, aria-owned subtree was shown and aria-activedescendant was simultaneously targeted inside it, aria-activedescendant would fail.
This occurred because when we processed insertions, the presence of aria-owns meant we didn't create the subtree.
This meant that when we processed aria-activedescendant (which occurred before relocations), the active descendant didn't exist yet.
To fix this, we now process generic notifications (including aria-activedescendant) *after* relocations.
Differential Revision: https://phabricator.services.mozilla.com/D40579
--HG--
extra : moz-landing-system : lando
When PersistentBufferProviderShared::ClearCachedResources() is called, PersistentBufferProviderShared keeps front TextureClient. But TextureHost's read lock might be released by host side. Then TextureClient's read lock could not be used for checking if the TexutreClient is used by host side.
Differential Revision: https://phabricator.services.mozilla.com/D40440
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
CSS: WPT for font-variation-settings parsing
font-variation-settings is 'normal' or a comma-delimited
list of string - number pairs.
Each string is 4 characters.
https://drafts.csswg.org/css-fonts-4/#font-variation-settings-def
Change-Id: I9ecd80be68a1575647f4dc64864640bc36ee2b64
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728583
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682685}
--
wpt-commits: 6793ad0be089311e6e04e151a3807c7ca9212e2c
wpt-pr: 18198
