It looks like there is only networkEventUpdate which isn't 100% correctly typed.
It appears in specs, but one test (test_network_security-hpkp.html) is still failing if we remove it.
Differential Revision: https://phabricator.services.mozilla.com/D54205
--HG--
extra : moz-landing-system : lando
This patch:
- Removes the responsiveness feature from the default features since we don't
have it anymore.
- Adds "Renderer" thread to the default threads list. That is needed to capture
screenshots with webrender.
Depends on D55103
Differential Revision: https://phabricator.services.mozilla.com/D55158
--HG--
extra : moz-landing-system : lando
Some text in the toolbar wasn't properly vertically aligned in this interface.
Differential Revision: https://phabricator.services.mozilla.com/D54743
--HG--
extra : moz-landing-system : lando
The test is sometimes failing because there's a pending
connection to the server while the connection is closed.
My guess is that somehow the test could have been checking
other nodes instead of the current evaluated on to wait
for a node to be fully expanded.
The fix made here is to make sure that we only have one
node displayed when testing the object inspector.
Differential Revision: https://phabricator.services.mozilla.com/D54943
--HG--
extra : moz-landing-system : lando
Right now it's enable but it throws with "remove() is not a function".
Depends on D55096
Differential Revision: https://phabricator.services.mozilla.com/D55097
--HG--
extra : moz-landing-system : lando
As they have an innerHTML property, and it is useful.
I didn't find relevant tests for this. browser_inspector-traversal.js tests only
the server bits.
Differential Revision: https://phabricator.services.mozilla.com/D54422
--HG--
extra : moz-landing-system : lando
We were logging a concatenated string of the
exception and its stack trace, which means
that it would show up in the console as a simple
string (i.e. without clickable links).
Logging the exception should make it more readable
in the browser console.
Differential Revision: https://phabricator.services.mozilla.com/D54889
--HG--
extra : moz-landing-system : lando
People do like to use zoom along with transforms for legit reasons, which means
that we get this wrong.
This is unfortunate, as the whole point of the hack was fixing sites that only
used zoom without regressing sites that would do:
zoom: 0.5;
-moz-transform: scale(0.5);
transform-origin: 0 0;
So we're a bit stuck here. The only way to deal with the known regressions is
parsing `zoom: 1` as invalid, which is insane, and it would probably cause other
compat issues... For now disable the pref.
Differential Revision: https://phabricator.services.mozilla.com/D54685
--HG--
extra : moz-landing-system : lando
This allows consumers to directly require a single Rep file
if needed (e.g. the inspector only needs elementNode or textNode).
In order to make this work, the requires for react-dom-factories
and prop-types needed to be changed to the in-tree modules.
We also needed to modified the reps jest config, as well as the
babel config so we can run tests and still generate the reps bundle.
Finally, the dom-node-constants is modified to not use define as
it's not used as an AMD module.
Differential Revision: https://phabricator.services.mozilla.com/D54680
--HG--
extra : moz-landing-system : lando
This only affects console api calls where one of the
argument is an empty string. Since we don't quote
string arguments for those, it was difficult to spot
an empty string there.
Jest test are added, as well as a mochitest for the
console to make sure that we don't have unwanted
side effects (for evaluation results, object with
empty string properties, ...)
Differential Revision: https://phabricator.services.mozilla.com/D54687
--HG--
extra : moz-landing-system : lando
PerformanceEntry values are put in the `getterValue` property in
the descriptor, so whenever we want to display a table we need
to check if the value could be in there.
This highlighted an issue in the console layout when there is a
large number of cells, which we fix in this patch.
Differential Revision: https://phabricator.services.mozilla.com/D54261
--HG--
extra : moz-landing-system : lando
Increasing the number of columnns highlighted some issues:
- Some element could be off-screen, the grid-template-columns
needed to be adjusted
- headers could be cut-off, we add a title on the element to
have the full content in a tooltip
- properties that are not defined were displayed as "undefined",
which is not really true, and take a lot of space. We render
them as an empty cell in such case now.
A test is added to check the max-column limit.
Differential Revision: https://phabricator.services.mozilla.com/D54260
--HG--
extra : moz-landing-system : lando
Nicolas Chevobbe
Alexandre Poirot
Emilio Cobos Álvarez
Nazım Can Altınova
Yura Zenevich
Sorin Davidoi
hayden
Neil Deakin
Daisuke Akatsuka
Noemi Erli
jaril
Jason Laster
Mihai Alexandru Michis
Julian Descottes
Bryan Kok
Michael Ratcliffe
Sylvestre Ledru