This includes the following API:
* Debugger.Object.prototype.createSource
* startColumn field of the parameter object
* Debugger.Script.prototype.startColumn
* return value
* Debugger.Script.prototype.getPossibleBreakpoints
* minColumn and maxColumn property of the query
* columnNumber property of the returned array elements
* Debugger.Script.prototype.getOffsetMetadata
* columnNumber property of the returned array elements
* Debugger.Script.prototype.getOffsetLocation
* columnNumber property of the returned array elements
* Debugger.Script.prototype.getAllColumnOffsets
* columnNumber property of the returned array elements
* Debugger.Script.prototype.getOffsetsCoverage
* columnNumber property of the returned array elements
* Debugger.Source.prototype.startColumn
* return value
This patch modifies DevTools code to convert the column number from/to 1-origin,
while keep using 0-origin on their side.
One exception is the WASM's column number, which had been using 1-origin 1.
Each consumer in DevTools handles the WASM case, and the code can be removed
once DevTools internal also switches to 1-origin column number.
The other exception is to use 1-based column number in logCustomFormatterError,
which is folded from bug 1864783 patch.
Differential Revision: https://phabricator.services.mozilla.com/D193270
This includes the following API:
* Debugger.Object.prototype.createSource
* startColumn field of the parameter object
* Debugger.Script.prototype.startColumn
* return value
* Debugger.Script.prototype.getPossibleBreakpoints
* minColumn and maxColumn property of the query
* columnNumber property of the returned array elements
* Debugger.Script.prototype.getOffsetMetadata
* columnNumber property of the returned array elements
* Debugger.Script.prototype.getOffsetLocation
* columnNumber property of the returned array elements
* Debugger.Script.prototype.getAllColumnOffsets
* columnNumber property of the returned array elements
* Debugger.Script.prototype.getOffsetsCoverage
* columnNumber property of the returned array elements
* Debugger.Source.prototype.startColumn
* return value
This patch modifies DevTools code to convert the column number from/to 1-origin,
while keep using 0-origin on their side.
One exception is the WASM's column number, which had been using 1-origin 1.
Each consumer in DevTools handles the WASM case, and the code can be removed
once DevTools internal also switches to 1-origin column number.
The other exception is to use 1-based column number in logCustomFormatterError,
which is folded from bug 1864783 patch.
Differential Revision: https://phabricator.services.mozilla.com/D193270
This documents how one can wirelessly debug a Firefox for Android app
over Wi-Fi, without requiring a USB cable.
The steps here differ from the official documentation at
https://developer.android.com/tools/adb#connect-to-a-device-over-wi-fi
in the following ways:
- Omitted unnecessary dependency on Android Studio.
- Added instruction to look up the IP address from Internet / Wi-Fi
settings instead of relying on the displayed IP address. The latter
is not reliable, e.g. when a VPN is enabled.
- Added explicit instruction to use "adb connect" to avoid dependency
on mDNS.
Differential Revision: https://phabricator.services.mozilla.com/D193390
- Rename the general section to `ignoring sources`
- Update the image for the ignore a source section
- Added content and images for ignore line and ignore lines
Differential Revision: https://phabricator.services.mozilla.com/D179316
These preferences ended up being specifics to network observation.
The only one lastly supported is now set via NetworkParentActor.setSaveRequestAndResponseBodies.
Differential Revision: https://phabricator.services.mozilla.com/D165864
With the removal of the old non-fission browser toolbox,
we removed the last usage of this old codebase.
We used to be able to listen to network events via WebConsole's actor's startListeners method.
Nowadays we should rather use the Watcher actor's watchResources method and listen to
NETWORK_EVENT resource.
(or migrate to WebDriver Bidi which will soon allow to listen to network requests see bug 1790369)
This patch also removed all now unused block* requests from webconsole actor,
Differential Revision: https://phabricator.services.mozilla.com/D165603
This migrate gDevTools.showToolbox, but also the Toolbox now receives a commands right away,
and no longer need to create commands out of the descriptor front.
I'm removing browser_two_tabs as it is focusing on testing Tab Descriptors (RootFront.listTabs+getTab)
and Tab targets (TabDescriptor.getTarget).
Using getTarget on descriptor is legacy codepath for a while now.
We should now rather cover commands instead of these low level RDP methods.
Differential Revision: https://phabricator.services.mozilla.com/D157796
This migrate gDevTools.showToolbox, but also the Toolbox now receives a commands right away,
and no longer need to create commands out of the descriptor front.
I'm removing browser_two_tabs as it is focusing on testing Tab Descriptors (RootFront.listTabs+getTab)
and Tab targets (TabDescriptor.getTarget).
Using getTarget on descriptor is legacy codepath for a while now.
We should now rather cover commands instead of these low level RDP methods.
Differential Revision: https://phabricator.services.mozilla.com/D157796
This migrate gDevTools.showToolbox, but also the Toolbox now receives a commands right away,
and no longer need to create commands out of the descriptor front.
I'm removing browser_two_tabs as it is focusing on testing Tab Descriptors (RootFront.listTabs+getTab)
and Tab targets (TabDescriptor.getTarget).
Using getTarget on descriptor is legacy codepath for a while now.
We should now rather cover commands instead of these low level RDP methods.
Differential Revision: https://phabricator.services.mozilla.com/D157796