Bug 1637616 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by

Gabriel [:gl] (ΦωΦ)

on 2020-05-13 07:35:15 PDT

I was trying to make Private Relay's popup.html mobile responsive in [fx-private-relay#258](https://github.com/mozilla/fx-private-relay/pull/259), which had me trying to inspect the markup of popup.html while Firefox Private Relay is running on my Android device or emulator.

STR:
1. Download the XPI of Firefox Private Relay locally from AMO. 
`wget https://addons.mozilla.org/firefox/downloads/file/3556483/private_relay-1.3.0-fx.xpi`
2. Launch Firefox Private Relay on your Android device or Android emulator. See https://github.com/mozilla/fx-private-relay/pull/254#issuecomment-622964146 for instructions on how to do that.
3. Open `about:debugging` and connect to your Android device or Android emulator.
4. Click on `Inspect` for Private Relay and Multiprocess Toolbox.
5. Notice that the markup is not loaded in the Private Relay remote debugging toolbox (maybe that is the desired behaviour?). In the Multiprocess Toolbox, you can search for ids/classes that are on the popup.html in the markup view searchbox, but they do not appear on the markup view.

Some errors I do see:
```
TypeError: can't access property "setDebugTargetData", this.component is undefined
    _setDebugTargetData resource://devtools/client/framework/toolbox.js:4229
    _onNavigate resource://devtools/client/framework/toolbox.js:4218
    _emit resource://devtools/shared/event-emitter.js:226
    emit resource://devtools/shared/event-emitter.js:172
    emit resource://devtools/shared/event-emitter.js:324
    _onTabNavigated resource://devtools/client/fronts/targets/browsing-context.js:76
    _emit resource://devtools/shared/event-emitter.js:226
    emit resource://devtools/shared/event-emitter.js:172
    emit resource://devtools/shared/event-emitter.js:324
    onPacket resource://devtools/shared/protocol/Front.js:294
    onPacket resource://devtools/client/devtools-client.js:493
    _onJSONObjectReady resource://devtools/shared/transport/transport.js:464
    makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
    makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
event-emitter.js:241:21
```

Closing the tab to the Private Relay toolbox and Multiprocess toolbox, and reopening through their respective `Inspect` buttons in about:debugging throws the following:
```
Exception when calling onAvailable handler Protocol error (noSuchActor): No such actor for ID: server0.conn1.child34/consoleActor2 from: server0.conn1.child34/consoleActor2 Error: Protocol error (noSuchActor): No such actor for ID: server0.conn1.child34/consoleActor2 from: server0.conn1.child34/consoleActor2
    onPacket resource://devtools/shared/protocol/Front.js:319
    DevTools RDP*request resource://devtools/shared/protocol/Front.js:256
    name resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:47
    startListeners resource://devtools/client/fronts/webconsole.js:519
    attachConsole resource://devtools/client/fronts/targets/target-mixin.js:448
    _attach resource://devtools/client/fronts/targets/browsing-context.js:100
    attach resource://devtools/client/fronts/targets/browsing-context.js:102
    _attachTarget resource://devtools/client/framework/toolbox.js:768
    _onTargetAvailable resource://devtools/client/framework/toolbox.js:739
    promises resource://devtools/shared/resources/target-list.js:329
    watchTargets resource://devtools/shared/resources/target-list.js:324
    open resource://devtools/client/framework/toolbox.js:844
    open resource://devtools/client/framework/toolbox.js:988
    createToolbox resource://devtools/client/framework/devtools.js:622
    showToolbox resource://devtools/client/framework/devtools.js:509
    initToolbox chrome://devtools/content/framework/toolbox-init.js:152
    async* chrome://devtools/content/framework/toolbox-init.js:162
target-list.js:338:19
```

```
Exception when calling onAvailable handler Protocol error (noSuchActor): No such actor for ID: server0.conn1.child34/inspectorActor3 from: server0.conn1.child34/inspectorActor3 Error: Protocol error (noSuchActor): No such actor for ID: server0.conn1.child34/inspectorActor3 from: server0.conn1.child34/inspectorActor3
    onPacket resource://devtools/shared/protocol/Front.js:319
    DevTools RDP*request resource://devtools/shared/protocol/Front.js:256
    name resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:47
    _getWalker resource://devtools/client/fronts/inspector.js:64
    initialize resource://devtools/client/fronts/inspector.js:43
    manage resource://devtools/shared/protocol/Front.js:116
    getFront resource://devtools/shared/protocol/types.js:609
    getFront resource://devtools/client/fronts/targets/target-mixin.js:305
    initInspectorFront resource://devtools/client/inspector/inspector.js:244
    _onTargetAvailable resource://devtools/client/inspector/inspector.js:222
    promises resource://devtools/shared/resources/target-list.js:329
    watchTargets resource://devtools/shared/resources/target-list.js:324
    init resource://devtools/client/inspector/inspector.js:198
    open resource://devtools/client/inspector/panel.js:12
    onLoad resource://devtools/client/framework/toolbox.js:2529
target-list.js:338:19
```

Revision 1 by

Gabriel [:gl] (ΦωΦ)

on 2020-05-13 07:52:58 PDT

I was trying to make Private Relay's popup.html mobile responsive in [fx-private-relay#258](https://github.com/mozilla/fx-private-relay/pull/259), which had me trying to inspect the markup of popup.html while Firefox Private Relay is running on my Android device or emulator.

STR:
1. Download the XPI of Firefox Private Relay locally from AMO. 
`wget https://addons.mozilla.org/firefox/downloads/file/3556483/private_relay-1.3.0-fx.xpi`
2. Launch Firefox Private Relay on your Android device or Android emulator. See https://github.com/mozilla/fx-private-relay/pull/254#issuecomment-622964146 for instructions on how to do that.
3. Open `about:debugging` and connect to your Android device or Android emulator.
4. Click on `Inspect` for Private Relay and Multiprocess Toolbox.
5. Select `popup.html` from the iframe picker.
6. Notice that the markup is not loaded in the Private Relay remote debugging toolbox (maybe that is the desired behaviour?). In the Multiprocess Toolbox, you can search for ids/classes that are on the popup.html in the markup view searchbox, but they do not appear on the markup view.

Some errors I do see:
```
TypeError: can't access property "setDebugTargetData", this.component is undefined
    _setDebugTargetData resource://devtools/client/framework/toolbox.js:4229
    _onNavigate resource://devtools/client/framework/toolbox.js:4218
    _emit resource://devtools/shared/event-emitter.js:226
    emit resource://devtools/shared/event-emitter.js:172
    emit resource://devtools/shared/event-emitter.js:324
    _onTabNavigated resource://devtools/client/fronts/targets/browsing-context.js:76
    _emit resource://devtools/shared/event-emitter.js:226
    emit resource://devtools/shared/event-emitter.js:172
    emit resource://devtools/shared/event-emitter.js:324
    onPacket resource://devtools/shared/protocol/Front.js:294
    onPacket resource://devtools/client/devtools-client.js:493
    _onJSONObjectReady resource://devtools/shared/transport/transport.js:464
    makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
    makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
event-emitter.js:241:21
```

Closing the tab to the Private Relay toolbox and Multiprocess toolbox, and reopening through their respective `Inspect` buttons in about:debugging throws the following:
```
Exception when calling onAvailable handler Protocol error (noSuchActor): No such actor for ID: server0.conn1.child34/consoleActor2 from: server0.conn1.child34/consoleActor2 Error: Protocol error (noSuchActor): No such actor for ID: server0.conn1.child34/consoleActor2 from: server0.conn1.child34/consoleActor2
    onPacket resource://devtools/shared/protocol/Front.js:319
    DevTools RDP*request resource://devtools/shared/protocol/Front.js:256
    name resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:47
    startListeners resource://devtools/client/fronts/webconsole.js:519
    attachConsole resource://devtools/client/fronts/targets/target-mixin.js:448
    _attach resource://devtools/client/fronts/targets/browsing-context.js:100
    attach resource://devtools/client/fronts/targets/browsing-context.js:102
    _attachTarget resource://devtools/client/framework/toolbox.js:768
    _onTargetAvailable resource://devtools/client/framework/toolbox.js:739
    promises resource://devtools/shared/resources/target-list.js:329
    watchTargets resource://devtools/shared/resources/target-list.js:324
    open resource://devtools/client/framework/toolbox.js:844
    open resource://devtools/client/framework/toolbox.js:988
    createToolbox resource://devtools/client/framework/devtools.js:622
    showToolbox resource://devtools/client/framework/devtools.js:509
    initToolbox chrome://devtools/content/framework/toolbox-init.js:152
    async* chrome://devtools/content/framework/toolbox-init.js:162
target-list.js:338:19
```

```
Exception when calling onAvailable handler Protocol error (noSuchActor): No such actor for ID: server0.conn1.child34/inspectorActor3 from: server0.conn1.child34/inspectorActor3 Error: Protocol error (noSuchActor): No such actor for ID: server0.conn1.child34/inspectorActor3 from: server0.conn1.child34/inspectorActor3
    onPacket resource://devtools/shared/protocol/Front.js:319
    DevTools RDP*request resource://devtools/shared/protocol/Front.js:256
    name resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:47
    _getWalker resource://devtools/client/fronts/inspector.js:64
    initialize resource://devtools/client/fronts/inspector.js:43
    manage resource://devtools/shared/protocol/Front.js:116
    getFront resource://devtools/shared/protocol/types.js:609
    getFront resource://devtools/client/fronts/targets/target-mixin.js:305
    initInspectorFront resource://devtools/client/inspector/inspector.js:244
    _onTargetAvailable resource://devtools/client/inspector/inspector.js:222
    promises resource://devtools/shared/resources/target-list.js:329
    watchTargets resource://devtools/shared/resources/target-list.js:324
    init resource://devtools/client/inspector/inspector.js:198
    open resource://devtools/client/inspector/panel.js:12
    onLoad resource://devtools/client/framework/toolbox.js:2529
target-list.js:338:19
```

Back to Bug 1637616 Comment 0