Bug 1825215 Comment 2 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
on 
Hello,

I reproduced the issue on the latest Nightly (113.0a1/20230330214245), Beta (112.0b9/20230330182947) and Release (111.0.1/20230321111920) under Windows 10 x64 and macOS 11.3.1.

Using the attached extension, which I modified to have manifest version 3 and include the `scripting` and `activeTab` permissions, running the `browser.scripting.executeScript({target: {tabId: -1}, func: () => true}). catch(error => console.error({error}))` code in the extensions console results in the error mentioned in Comment 0.

For more details, see the attached screenshot.
Revision 1 by
on 
Hello,

I reproduced the issue on the latest Nightly (113.0a1/20230330214245), Beta (112.0b9/20230330182947) and Release (111.0.1/20230321111920) under Windows 10 x64 and macOS 11.3.1.

Using the attached extension (part of the example extensions pack available on MDN), which I modified to have manifest version 3 and include the `scripting` and `activeTab` permissions, running the `browser.scripting.executeScript({target: {tabId: -1}, func: () => true}). catch(error => console.error({error}))` code in the extensions console results in the error mentioned in Comment 0.

For more details, see the attached screenshot.

Back to Bug 1825215 Comment 2