Bugzilla

The events do not fire because internally the request is considered redirected for some reason.

If you modify the test case and add `filter.onerror = e => console.error(filter.error);`

... then the displayed error is (confusingly) `"Invalid request ID"`
This error is confusing due to bug 1683862.

I tried out the STR with `about:addons`, `about:config`, `about:preferences`, `about:logo` can can confirm the observations.
On the other hand, on `about:newtab`, `about:privatebrowsing`, `https://addons.mozilla.org/` the issue does not happen.

Based on this, I think that the actual issue is happening when a navigation is triggered from a tab in a non-remote process to a remote process.
To test this hypothesis, I set `extensions.webextensions.remote` to `false` in `about:config`, restarted Firefox, and indeed, the issue also reproduced there.

Next step here is to investigate what is happening and triage further.

The events do not fire because internally the request is considered redirected for some reason.

If you modify the test case and add `filter.onerror = e => console.error(filter.error);`

... then the displayed error is (confusingly) `"Invalid request ID"`
This error is confusing due to bug 1683862.

I tried out the STR with `about:addons`, `about:config`, `about:preferences`, `about:logo` can can confirm the observations.
On the other hand, on `about:newtab`, `about:privatebrowsing`, `https://addons.mozilla.org/` the issue does not happen.

Based on this, I think that the actual issue is happening when a navigation is triggered from a tab in a non-remote process to a remote process.
To test this hypothesis, I set `extensions.webextensions.remote` to `false` in `about:config`, restarted Firefox, opened the `manifest.json` link of the extension, and indeed, the issue also reproduced there.

Next step here is to investigate what is happening and triage further.