For compatibility with Chrome, when removing inline style at block parent,
we should reset the style with creating `<span>` element whose `style`
attribute removes the style. We do this only in CSS mode, but we should do
it in HTML mode too.
This patch also makes `FontFaceStateCommand::SetState()` ignore `tt` value
if its root caller is `Document::ExecCommand()`. It was implemented for
composer to handle XUL command in bug 115922. Therefore, we should not do
this special handling on the web. If it were possible to separate this
change to another bug, it'd be nicer. But without this change, we'll have
a lot of regressions of `Document.execCommand("fontname")`. Therefore,
this is also fixed in this patch.
Note that this removes first `.ini` file selection because
the tests cannot be run without test number range parameter.
So, the sections are not used anymore.
Differential Revision: https://phabricator.services.mozilla.com/D47862
--HG--
extra : moz-landing-system : lando
When high contrast mode is enabled, title bar is drawn as transparent and on-client area rendering by DWM is shown. But when compositor window in GPU process is used, the on-client area rendering was not shown. To address the proboem, window needs to be cleard as transparent and SwapChain of compositor window needs to be DXGI_ALPHA_MODE_PREMULTIPLIED.
WinCompositorWidget::mTransparencyMode is changed to atomic, since it is accessed from compositor thread and render thread.
Differential Revision: https://phabricator.services.mozilla.com/D48302
--HG--
extra : moz-landing-system : lando
This extends AutoSetThreadIsSweeping to take an optional zone parameter. When querying the marking state via IsAboutToBeFinalized and IsMarked calls we check this zone matches the zone of the thing we're looking at.
Differential Revision: https://phabricator.services.mozilla.com/D48158
--HG--
extra : moz-landing-system : lando
The CanvasChild must be in the process of being destroyed at this point anyway.
Differential Revision: https://phabricator.services.mozilla.com/D47443
--HG--
extra : moz-landing-system : lando
For Glean, we are deprecating the use of bug numbers in metric metadata,
and moving to full URLs only. This removes the ambiguity between the
different trackers used by different projects (Bugzilla vs. Github, for
example), and will make the development of automated tools easier.
Differential Revision: https://phabricator.services.mozilla.com/D48455
--HG--
extra : moz-landing-system : lando
The rooted string was added in bug 966452, because at that point of time
`ownedReport.ucmessage` was a direct pointer to a JSString's character
storage. But now that we're already copying the JSString characters to UTF-8,
it's no longer necessary to keep the JSString alive through the ErrorReport.
Differential Revision: https://phabricator.services.mozilla.com/D48359
--HG--
extra : moz-landing-system : lando
As we would calculate time difference between frames by checking their timestamp, so we would always ensure that image has valid timestamp.
Differential Revision: https://phabricator.services.mozilla.com/D48034
--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
For compatibility with Chrome, when removing inline style at block parent,
we should reset the style with creating `<span>` element whose `style`
attribute removes the style. We do this only in CSS mode, but we should do
it in HTML mode too.
This patch also makes `FontFaceStateCommand::SetState()` ignore `tt` value
if its root caller is `Document::ExecCommand()`. It was implemented for
composer to handle XUL command in bug 115922. Therefore, we should not do
this special handling on the web. If it were possible to separate this
change to another bug, it'd be nicer. But without this change, we'll have
a lot of regressions of `Document.execCommand("fontname")`. Therefore,
this is also fixed in this patch.
Note that this removes first `.ini` file selection because
the tests cannot be run without test number range parameter.
So, the sections are not used anymore.
Differential Revision: https://phabricator.services.mozilla.com/D47862
--HG--
extra : moz-landing-system : lando
Surprisingly, its `aChildOnly` is never set to `true` and if it were set to
`true`, it does unnecessary recursive calls. Therefore, we can make it
simpler.
Differential Revision: https://phabricator.services.mozilla.com/D47860
--HG--
extra : moz-landing-system : lando
Test more of the ProfilerMarkerPayload's, all those from ProfilerMarkerPayload.h
that did not require external structures. (More to be added in the future.)
These tests focus on the profiler, by simulating markers as we expect them, and
verifying that the corresponding output is correct JSON as expected by the
frontend.
Differential Revision: https://phabricator.services.mozilla.com/D48327
--HG--
extra : moz-landing-system : lando
This does not test more markers than before. But instead of searching for
strings in the raw json, expected values are checked in the parsed output
profile.
Also some `ASSERT_...` tests could be changed to `EXPECT_...`, because their
failures would not prevent running more of the test.
Differential Revision: https://phabricator.services.mozilla.com/D48326
--HG--
extra : moz-landing-system : lando
NPAPI / Flash are EOL'ing in 2020, and we're unlikely to spend time trying to make
them work with Fission enabled. For now we can just disable these tests.
Differential Revision: https://phabricator.services.mozilla.com/D48444
--HG--
extra : moz-landing-system : lando
Previously, keyboard users had to press f6 several times to get to the doorhanger.
If a user is activating the doorhanger from the keyboard, it makes sense that they'd want to interact with it using the keyboard.
Differential Revision: https://phabricator.services.mozilla.com/D47719
--HG--
extra : moz-landing-system : lando
Populating them is hooked up for non-WebRender, with a comment outlining
possible implementation strategies for WebRender.
Differential Revision: https://phabricator.services.mozilla.com/D48384
--HG--
extra : moz-landing-system : lando
Stephen Horlander
Itiel
Sylvestre Ledru
Bob Owen
Valentin Gosu
Masayuki Nakano
sotaro
Jon Coppeard
Mark Banner
Dão Gottwald
Michael Droettboom
Cosmin Sabou
Martin Stransky
André Bargull
Zhao Jiazhong
Harry Twyford
Liang-Heng Chen
alwu
DimiDL
lloan
Andreea Pavel
Razvan Maries
Aaron Klotz
Gerald Squelart
Tom Prince
Daniel Varga
Kai Engert
Mike Conley
James Teh
Bogdan Tara
Brian Birtles
Boris Chiou
Botond Ballo