The .status element is turned into a simple <span> (instead of a <a>),
so it's 1. more semantically correct, and 2. doesn't create a new line.
We also handle null request `totalTime` by not showing the time in the status info,
as that could make the test to fail in chaos mode.
Differential Revision: https://phabricator.services.mozilla.com/D304391
Issue: After the sourcemap service has completed it should trigger and update which would cause `maybeScrollToBottomMessageCallback` ( which handles the auto scrolling)
to fire. But the `shouldScrollBottom` was failing, as it does not considrer the delayed updates which happen after the sourcemap service is done.
Differential Revision: https://phabricator.services.mozilla.com/D249904
This reverts commit fcd3970805.
Revert "Bug 1966005 - [devtools] Make sure to try auto-scroll after the completion of the sourcemap service r=devtools-reviewers,nchevobbe"
This reverts commit d6fc5d489d.
Revert "Bug 1959452 - [devtools] Throttle parent process events on the server side r=devtools-reviewers,jdescottes,ochameau"
This reverts commit b96015ae28.
Issue: After the sourcemap service has completed it should trigger and update which would cause `maybeScrollToBottomMessageCallback` ( which handles the auto scrolling)
to fire. But the `shouldScrollBottom` was failing, as it does not considrer the delayed updates which happen after the sourcemap service is done.
Differential Revision: https://phabricator.services.mozilla.com/D249904
The toolbox store is not available in the Browser Console.
The netmonitor's TabboxPanel component now exports two variants:
- TabboxPanel: raw TabboxPanel without toolbox store derived props
- ConnectedTabboxPanel: connected to the toolbox store for override props
Differential Revision: https://phabricator.services.mozilla.com/D241159
This is only to make the toggle works as before,
it doesn't handle persisting the toggle state
like in the Netmonitor.
We also pass `targetSearchResult` to `TabboxPanel` to avoid
unnecessary re-renders that were messing up the test.
Differential Revision: https://phabricator.services.mozilla.com/D238416
Requests can be blocked because of many reasons, but the label was always
saying it was because of DevTools.
Update the label so we follow what's done in Netmonitor.
Differential Revision: https://phabricator.services.mozilla.com/D210471
In some cases, we were getting null sourceId, which was causing an exception
to be thrown in `getFormattedSourceId` since it expects a string.
We add a simple guard in this function so we don't throw anymore.
But we shouldn't get null sourceId in the first place. It looks like for
some Wasm sources, the SavedFrame sourceId can be 0, which wasn't playing
well with some loose check we were doing in the sources manager.
Finally, the "Copy metadata" button we display when a console message crash
wasn't working. The message now includes the targetFront, which can be serialized
in JSON, so we simply ignore it.
Differential Revision: https://phabricator.services.mozilla.com/D206105
This feature is only exposed to internal usages of tracer.jsm, by passing traceStep boolean option:
```
startTracing({ global, traceSteps: true });
```
This will automatically log to stdout all traces, including each frame step within a function execution.
Without this flag, the tracer would only trace function calls and nothing more.
We would not know which line is being executed within the function execution.
Differential Revision: https://phabricator.services.mozilla.com/D201977
Also allow logging trace whenever any DOM Element get added, removed or modified.
For now this is exposed only via the console command via:
:tracer --dom-mutations (for all types of mutation)
:tracer --dom-mutations add,attributes,remove (coma separated list of mutation types you want to listen for)
Also revise the handling of "isWorker" so that all checks have the best possible check.
Differential Revision: https://phabricator.services.mozilla.com/D201976
The "is in opening group" computation, which goes through all message arrays
can be avoided until it is meaningful to check for this particular edge case.
Also we can remove the redundant check against `nextProps.messagesUi`.
Differential Revision: https://phabricator.services.mozilla.com/D197770
Updating eslint-plugin-react to 7.33.2 raises new eslint errors.
A few component needed to have their proptypes fixed (or added).
JSPropertyProvider was considered as a react component by the plugin,
I guess because it is a function starting with an uppercase letter.
Since it is a bit unusual to have such thing, I renamed it slightly
to make it look more like a function.
Differential Revision: https://phabricator.services.mozilla.com/D197596
This help reduce the RDP overhead by only transferring what is strictly necessary.
The console message resources bundles various useless attributes.
This also help use a custom rendering in the frontend so that traces can
be displayed distinctly and differently from the console API calls.
Differential Revision: https://phabricator.services.mozilla.com/D196020
This help reduce the RDP overhead by only transferring what is strictly necessary.
The console message resources bundles various useless attributes.
This also help use a custom rendering in the frontend so that traces can
be displayed distinctly and differently from the console API calls.
Differential Revision: https://phabricator.services.mozilla.com/D196020
Nicolas Chevobbe