`MediaControlKeysEvent` should represent possible control key events, so adding a non-existing `eNone` in this class is not good.
Differential Revision: https://phabricator.services.mozilla.com/D57022
--HG--
extra : moz-landing-system : lando
Currently, it's possible for testFetchStreamError to finish receiving data
before the error is received and throws.
Differential Revision: https://phabricator.services.mozilla.com/D56797
--HG--
extra : moz-landing-system : lando
This will allow us to know whether a certain window is controlled GeckoView or
not in the content process.
Differential Revision: https://phabricator.services.mozilla.com/D56651
--HG--
extra : moz-landing-system : lando
`TextInputHandler::HandleFlagsChanged()` dispatches `keydown` and `keyup`
events even if the native key code is not set properly because web apps
and our internal component like EventStateManager may cache modifier
state with listening to `keydown` and `keyup` events.
If native event does not have proper key code value, it computes key code
from recorded key code value for each flag, but one modifier key may
set 2 or more flags. Therefore, it should check whether the computed
key code's event has already been dispatched or not.
Differential Revision: https://phabricator.services.mozilla.com/D56138
--HG--
extra : moz-landing-system : lando
NOTIFY_IME_OF_FOCUS performs lazy initialization for text dispatcher. When
GeckoViewSupport attaches GeckoEditable during initialization,
GeckoEditableSupport destroys myself.
If GeckoEditable already has focus, don't destroy GeckoEditable child.
Also, I want to add debug warning to debug like this issue.
Differential Revision: https://phabricator.services.mozilla.com/D55914
--HG--
extra : moz-landing-system : lando
This is generally pretty straightforward, and rewrites nearly all calls. It
skips the ones that it can detect using frame script globals like
`sendAsyncMessage`, though.
Differential Revision: https://phabricator.services.mozilla.com/D53740
--HG--
extra : moz-landing-system : lando
Add `Open()` to support inherited sources to implement their own initialization and also don't hold the reference of the source if it fails to initialize.
Differential Revision: https://phabricator.services.mozilla.com/D56449
--HG--
extra : moz-landing-system : lando
Add an ability for inherited sources to implement their own deconstruction operations.
Differential Revision: https://phabricator.services.mozilla.com/D56447
--HG--
extra : moz-landing-system : lando
Changes:
For the time being, mark the test as expected failure on ubuntu1804, since the values the test checks for are coded in the test and need to be updated once platform against which test runs is updated to ubuntu1804.
Differential Revision: https://phabricator.services.mozilla.com/D56466
--HG--
extra : moz-landing-system : lando
This intended to fix some windows builds, but that didn't end up working.
This removes some unused members and such, and fixes some missing includes
that they uncover (whoops).
This was needed because some windows headers used in the sandbox redefine STRICT
(which is used by `StyleContain`) and `TRANSPARENT`, which is used by some WR
stuff.
Differential Revision: https://phabricator.services.mozilla.com/D56317
--HG--
extra : moz-landing-system : lando
We want the print job title set when actually submitting the job to a printer
so that the job appears with a useful title in any print job management
software the user may be using. However, we do that in
nsDeviceContextSpecX::BeginDocument, which is the place that it needs to
happen.
This removed code is called much earlier, while setting up to open the print
dialog and using a temporary nsPrintSettingsX in order to configure the
dialog. The dialog does not make use of the print job name (and we discard
the nsPrintSettingsX before going on to do the print using BeginDocument).
This removes the last piece of code that requires us to pass a
nsIWebBrowserPrint to the print dialog opening code. Removing that clears the
way to simplify the code and get printing working with Fission enabled.
Differential Revision: https://phabricator.services.mozilla.com/D56087
--HG--
extra : moz-landing-system : lando
For a PMSession to be given a job name, the job name must be set on the
PMPrintSettings before it is passed to PMSessionBeginCGDocumentNoDialog.
However, since nsDeviceContext::BeginDocument calls PrintTarget::BeginPrinting
before calling nsDeviceContextSpec::BeginDocument, the setting of the job name
in nsDeviceContextSpecX::BeginDocument was happening after the
PMSessionBeginCGDocumentNoDialog call in PrintTargetCG::BeginPrinting, and was
doing us no good. This moves the job name setting into
PrintTargetCG::BeginPrinting so that the job name is set first.
Note: The job name is shown if your printer/OS has software to manage the list
of queued jobs waiting to print.
Differential Revision: https://phabricator.services.mozilla.com/D56241
--HG--
extra : moz-landing-system : lando
This is generally pretty straightforward, and rewrites nearly all calls. It
skips the ones that it can detect using frame script globals like
`sendAsyncMessage`, though.
Differential Revision: https://phabricator.services.mozilla.com/D53740
--HG--
extra : moz-landing-system : lando
Create a general interface for getting platform-specific media keys event source in order to remove platform specific code from non-platform related folder `dom/media`.
Differential Revision: https://phabricator.services.mozilla.com/D55892
--HG--
rename : dom/media/mediacontrol/MediaHardwareKeysEventSourceMac.h => widget/cocoa/MediaHardwareKeysEventSourceMac.h
rename : dom/media/mediacontrol/MediaHardwareKeysEventSourceMac.mm => widget/cocoa/MediaHardwareKeysEventSourceMac.mm
extra : moz-landing-system : lando
The current shutdown phase is too early and thus may crash when called
by `UntrustedModulesProcessor`. We move it to a later phase such that the
processor has already shut down.
Differential Revision: https://phabricator.services.mozilla.com/D53683
--HG--
extra : moz-landing-system : lando
`LauncherResult` only includes file and line info when built into the launcher
process. Now that there will be `xul.dll`-based code calling into launcher
process startup, this would create an ABI mismatch.
This patch creates a new type, `LauncherResultWithLineInfo`, that
unconditionally includes the file and line so that APIs called by both `xul`
and non-`xul` code can have the same ABI for both.
Differential Revision: https://phabricator.services.mozilla.com/D53677
--HG--
extra : moz-landing-system : lando
This is generally pretty straightforward, and rewrites nearly all calls. It
skips the ones that it can detect using frame script globals like
`sendAsyncMessage`, though.
Differential Revision: https://phabricator.services.mozilla.com/D53740
--HG--
extra : moz-landing-system : lando
Alastor Wu
sotaro
Brian Grinstead
Noemi Erli
Brendan Dahl
Agi Sferro
Tom Ritter
Andreea Pavel
Emma Malysz
Gurzau Raul
Martin Stransky
Masayuki Nakano
Jeff Walden
Makoto Kato
shindli
Kris Maglione
Edwin Takahashi
Emilio Cobos Álvarez
Jonathan Watt
Daniel Varga
Aaron Klotz
Timothy Nikkel