Tapping the menu button during the panel has shown make the menu button to be unopenable. This cause reason is removing the pointer-events property before the mouse event happens.
The tapping event will happen many the event like the following:
1) touchstart
2) touchmove (Long tap only)
3) touchend
4) mousedown
5) mouseup
6) click
This patch will detect the touchend event to eat the click event.
Differential Revision: https://phabricator.services.mozilla.com/D7827
--HG--
extra : moz-landing-system : lando
For simplicity, we do not support remote-to-non-remote or non-remote-to-remote
nsIWebProgressListener persistence.
Differential Revision: https://phabricator.services.mozilla.com/D7936
--HG--
extra : moz-landing-system : lando
This patch removes linux64-jsdcov from the available builds on taskcluster along with any hacks used to run it. It also removes any 'coverage' entries that were added to skip tests.
Differential Revision: https://phabricator.services.mozilla.com/D7919
--HG--
extra : moz-landing-system : lando
Promises using defer are being replaced by new Promise and async await syntax. This is for the devtools/client/scratchpad directory.
Also includes refactoring of scratchpad for async await.
Differential Revision: https://phabricator.services.mozilla.com/D7247
--HG--
extra : moz-landing-system : lando
This duplicates all the mochitest, based tests except with
dom.serviceWorkers.parent_intercept set to true. For now they are only run on
mozilla-central with linux64/debug.
Differential Revision: https://phabricator.services.mozilla.com/D7641
--HG--
extra : moz-landing-system : lando
Currently, we block the markup and all other sidebar panels from rendering their
content until the markup iframe is loaded. So, we prevent this by setting the
default node front at the beginning.
We also move all the remaining event handlers to prevent unnecessary events
since this is the first time the inspector is being constructed. In particular,
we move the "new-node-front" event handler and manually call the actions that
are performed in onNewSelection to prevent these updates from taking place
until all the components are initialized.
Depends on D7405. The adb-addon module fires events whenever the
addon state changes, so Devices.jsm should be able to simply reuse this
module to update its internal state, rather than having adb-addon set
something on Devices.jsm directly.
On a sidenote, we really should not propagate the adb status via Devices.jsm
but since WebIDE relies on this, I decided to keep the code as is for now.
We will remove it from Devices.jsm when WebIDE is removed.
Differential Revision: https://phabricator.services.mozilla.com/D7406
--HG--
extra : moz-landing-system : lando
Depends on D7404. The install method should not hardcode "webide"
for the addon manager telemetry info
Differential Revision: https://phabricator.services.mozilla.com/D7405
--HG--
extra : moz-landing-system : lando
Depends on D7403
The getADBAddon/forgetADBAddon is not removing listeners or doing
anything useful since the next call to getADBADdon will just recreate an
instance of ADBAddon. We can expose a singleton and use lazy requires to
achieve the same effect
Differential Revision: https://phabricator.services.mozilla.com/D7404
--HG--
extra : moz-landing-system : lando
Noemi Erli
Tiberius Oros
Andreea Pavel
Neil Deakin
Mantaroh Yoshinaga
Brian Hackett
Alexandre Poirot
Margareta Eliza Balazs
Patrick Brosset
yulia
Mike Conley
Gabriel Luong
Gregory Mierzwinski
sreeise
Andrew Halberstadt
Dorel Luca
Jason Laster
Daisuke Akatsuka
Csoregi Natalia
Gurzau Raul
Anshul Malik
Julian Descottes