Now, DevTools server is loaded with a custom loader every time we want to debug chrome
resources. We ensure toggling the "invisibleToDebugger" flag on Loader.jsm which itself
propagates to DevTools Sandboxes.
We added calls to force GC in console test to prevent crashes on Windows 7.
Differential Revision: https://phabricator.services.mozilla.com/D20347
--HG--
extra : moz-landing-system : lando
Refactors the logic so the target node on which the Font Editor operates can point to a parent node in case of text nodes without explicitly changing the node selection.
The target node is assigned to `this.node`. When that is null, it means the node selection is not supported by the Font Editor. This removes the need for the `isSelectedNodeValid()` method.
Differential Revision: https://phabricator.services.mozilla.com/D21387
--HG--
extra : moz-landing-system : lando
newSource events used to be sent on the target actors on FF66 and before,
this is no longer the case. But we still have to accept them if we connect
to old remotes, otherwise the events are considered as a method reply
and confuses packet ordering.
Differential Revision: https://phabricator.services.mozilla.com/D21394
--HG--
extra : moz-landing-system : lando
When reviewing https://bugzilla.mozilla.org/show_bug.cgi?id=1521052 I did not think about Firefox for Android which is not using e10s.
This means the main DebuggerServer will be killed when there are no connections left. Happy to discuss more about the preferred solution.
This is a regression in 66 and I hope to uplift a fix for this.
Differential Revision: https://phabricator.services.mozilla.com/D20830
--HG--
extra : moz-landing-system : lando
Refactors the logic so the target node on which the Font Editor operates can point to a parent node in case of text nodes without explicitly changing the node selection.
The target node is assigned to `this.node`. When that is null, it means the node selection is not supported by the Font Editor. This removes the need for the `isSelectedNodeValid()` method.
Differential Revision: https://phabricator.services.mozilla.com/D21387
--HG--
extra : moz-landing-system : lando
The `yieldingEach` is moved into the only file that
is using it, in canvas debugger, and is not migrated
as the panel will be removed in a few months.
Differential Revision: https://phabricator.services.mozilla.com/D20641
--HG--
extra : moz-landing-system : lando
When large files's Response tab in Network Devtools is open, Firefox freezes. This checks for file size & switches from SourceEditor to pre() when the files is too big.
Differential Revision: https://phabricator.services.mozilla.com/D12450
--HG--
extra : moz-landing-system : lando
Now that the JsTerm is a React component, we shouldn't
let external consumers have to get the instance in order
to perform some actions on the console input.
We start with the most used actions, setInputValue and getInputValue,
and might extend that in the future.
Differential Revision: https://phabricator.services.mozilla.com/D20685
--HG--
extra : moz-landing-system : lando
This abstracts the most used console input functions,
and might make it easier to refactor things in the
future.
Differential Revision: https://phabricator.services.mozilla.com/D20684
--HG--
extra : moz-landing-system : lando
This patch make sure that all the helper functions
take the hud as a reference to the webconsole.
This makes them simpler to use as the user does not
have to remember what kind of object it takes.
We also rename some functions to not include the term
JsTerm, but rather console input, to make it easier
to reason about the code.
Differential Revision: https://phabricator.services.mozilla.com/D20683
--HG--
extra : moz-landing-system : lando
Renaming this property makes it easier to grasp what
it represents (instead of the vague `owner` term).
Differential Revision: https://phabricator.services.mozilla.com/D20678
--HG--
extra : moz-landing-system : lando
The goal of this deprecation notice is to inform people that these panels are going away. This code should be short lived, only firefox versions 67-68.
Differential Revision: https://phabricator.services.mozilla.com/D19518
--HG--
extra : moz-landing-system : lando
Depends on D20471
I can drop this changeset if we prefer, but this is how I imagine the disconnect button would fit in the RuntimeInfo.
Differential Revision: https://phabricator.services.mozilla.com/D20472
--HG--
extra : moz-landing-system : lando
Depends on D20464
For this change I moved all the layout logic for the RuntimeInfo h1 to RuntimeInfo.css
I don't know if we prefer to have layout info in base.css or in specialized components, but the RuntimeInfo header has a very specific structure.
I can't see how this would be worth having in base.css. And it is the only consumer for main-heading, so I removed all layout rules from base.css for main-heading.
Differential Revision: https://phabricator.services.mozilla.com/D20471
--HG--
extra : moz-landing-system : lando
Depends on D20439
I want to separate the addon checkbox and the load temporary addon for 2 reasons:
- we will get remove the checkbox after Bug 1525533
- we may support temporary addons for remote runtimes later
The "load temporary addon" might also move inside the Temporary Extensions category.
Differential Revision: https://phabricator.services.mozilla.com/D20464
--HG--
extra : moz-landing-system : lando
Alexandre Poirot
Jason Laster
Michael Ratcliffe
tanhengyeow
Cosmin Sabou
Razvan Caliman
lloan
Julian Descottes
Dorel Luca
Jonathan Kingston
Logan Smyth
Helena Moreno
saumya
Nicolas Chevobbe
Amy Chan
yulia
Jan-Ivar Bruaroey
Daisuke Akatsuka
Gurzau Raul
Andreea Pavel
Brian Hackett
Daniel Varga