Bugzilla

Follows a couple more details I noticed, in case they may be relevant to determine the appropriate fix:

- it looks like I can also hit the exact same exception (`global option is required in DevTools distinct global`) if I try to resend a network request originated from a webpage from the Browser Toolbox's network panel

- On the contrary it works as expected when I try the same from the tab's network panel that belongs to the webpage originating the request being resend from the network panel

- Adding `{ global: "contextual" }` to the ChromeUtils.defineESModuleGetters call from line 14 of devtools/server/actors/network-monitor/network-content.js did make both the network panel from the Addon Debugging toolbox and the network panel from the Browser Toolbox to not be hitting the same issue anymore (and in both cases it looked like the request was resend as expected)
   - resend the request from the tab's developer toolbox also seems to be still working with that addition

I'm not sure if Adding `{ global: "contextual" }`  option is the appropriate way to fix the underlying issue (or if it would be more like workarounding it, or if it does break anything else that I may not have tried nor noticed), but it felt still potentially relevant detail (along with the fact that the Browser Toolbox seems to also be hitting the same issue).

Follows a couple more details I noticed, in case they may be relevant to determine the appropriate fix:

- it looks like I can also hit the exact same exception (`global option is required in DevTools distinct global`) if I try to resend a network request originated from a webpage from the Browser Toolbox's network panel

- On the contrary it works as expected when I try the same from the tab's network panel that belongs to the webpage originating the request being resend from the network panel

- Adding `{ global: "contextual" }` to the ChromeUtils.defineESModuleGetters call from line 14 of devtools/server/actors/network-monitor/network-content.js did make both the network panel from the Addon Debugging toolbox and the network panel from the Browser Toolbox to not be hitting the same issue anymore (and in both cases it looked like the request was resend as expected)
   - resend the request from the tab's developer toolbox also seems to be still working with that addition

I'm not sure if adding `{ global: "contextual" }`  option is the appropriate way to fix the underlying issue (or if it would be more like workarounding it, or if it does break anything else that I may not have tried nor noticed), but it felt still potentially relevant detail (along with the fact that the Browser Toolbox seems to also be hitting the same issue).