This removes all the unimplemented RTCStats types from RTCStatsReport.webidl and deletes the related code
Differential Revision: https://phabricator.services.mozilla.com/D23276
--HG--
extra : moz-landing-system : lando
Templated pointer can't match |nullptr|, we should add overloading for
std::nullptr_t specifically to be able to support |nullptr|.
Differential Revision: https://phabricator.services.mozilla.com/D24925
--HG--
extra : moz-landing-system : lando
The only caller of `TouchManager::PreHandleEvent()` is
`PresShell::EventHandler::HandleEventWithCurrentEventInfo()` which is guaranteed
that it never handles untrused event by bug 1536353. Therefore, we can make
`PresShell::EventHandler::PrepareToDispatchEvent()` call it instead. That's
better place from the point of view of semantics and making
`PresShell::EventHandler::PrepareToDispatchEvent()` simpler.
Note that this may cause changing the score of a telemetry probe,
"INPUT_EVENT_QUEUED_APZ_TOUCH_MOVE_MS" because it will include the time of
the runtime cost of `TouchManager::PreHandleEvent()` when the event is an
`eTouchMove` event and handled by APZ. However, this was expired in 60.
So, we don't meet any changes with this patch actually.
Differential Revision: https://phabricator.services.mozilla.com/D24133
--HG--
extra : moz-landing-system : lando
On some low end GPUs, clip mask rendering can be a significant
GPU cost. One way to reduce this is to support segment rendering
on more primitive types, to reduce the size of clip masks.
This patch adds support for pictures that have clip masks
to take part in segment rendering. This can significantly
reduce the number of fragments that must be drawn into a clip
mask for off-screen picture surfaces.
In future, WR can take advantage of segment rendering to use
clip mask shaders that handle only a single corner at a time.
This will be a further significant performance win to clip mask
render time.
Differential Revision: https://phabricator.services.mozilla.com/D24852
--HG--
extra : moz-landing-system : lando
There's a lot of complexity around setting/unsetting the eagerCompilation flag.
It's simpler to determine this based on the warm-up threshold being 0.
The patch also fixes some jit-tests where this patch would result in a change in
behavior.
Differential Revision: https://phabricator.services.mozilla.com/D24155
--HG--
extra : moz-landing-system : lando
Storing this also in IonOptimizationLevels.h/cpp is more complicated than
necessary.
Differential Revision: https://phabricator.services.mozilla.com/D24154
--HG--
extra : moz-landing-system : lando
We used to have a different threshold for small functions but now they're both
set to 1000 so there's no need to special-case small functions.
Differential Revision: https://phabricator.services.mozilla.com/D24153
--HG--
extra : moz-landing-system : lando
While not required in the two examples provided, should those streams change resolution and continue to use the same type of bytstreams we would miss the changes as the keyframe never contains the new SPS/PPS NALs.
So we add an option to handle this case, so we can separate the cases where this could be needed without regressing bug 1469257
Differential Revision: https://phabricator.services.mozilla.com/D24854
--HG--
extra : moz-landing-system : lando
We limited the search for a SPS/PPS change to keyframe only in bug 1469257.
However this causes issues if the first frame containing a SPS/PPS isn't a keyframe.
We also need to error on content with no SPS/PPS as to inform the caller that something is amiss. Such content was invalid to start with.
Differential Revision: https://phabricator.services.mozilla.com/D24853
--HG--
extra : moz-landing-system : lando
This runs crashtests and reftests on ASAN builds with WR enabled, so
that we catch any ASAN regressions prior to landing without incurring
too great of a test load hit.
Differential Revision: https://phabricator.services.mozilla.com/D24952
--HG--
extra : moz-landing-system : lando
The new tokenizer, to make more natural typing restrictions like "?search terms", "search terms?" or "%my tab",
splits out restriction characters if they appear at the beginning or end of the search string. This means
keywords and aliases can't in general begin or end with a restriction character, but we don't have an input
check to prevent those.
For now the tokenizer can't recognize keywords or aliases, because it can't be made asynchronous until the
Quantum Bar is the default implementation, and anyway the complexity must be considered at that point.
The best we can do is to stop splitting out restriction character in the middle of the search string.
This will allow a part of the old interaction like searching for "keyword? something".
This patch also prevents us from splitting a %encoded string, fixing bug 1538715.
Differential Revision: https://phabricator.services.mozilla.com/D24929
--HG--
extra : moz-landing-system : lando
Make sure ProcessHandlerMixin.Process works also under 3.6.
3.6 introduced a _wait() method in its Popen class, that
conflicts with the one in mozprocess. The patch renames it
and also adds timeout where possible.
Differential Revision: https://phabricator.services.mozilla.com/D22157
--HG--
extra : moz-landing-system : lando
Call Reader:ResetZoom only in readermode and make resetFontSize async
***
make resetFontSize async
***
call Reader:ResetZoom only in readermode
***
Differential Revision: https://phabricator.services.mozilla.com/D24445
--HG--
extra : moz-landing-system : lando
