1736575 - Support execution world MAIN in `scripting.executeScript()`

Status: NEW

(WebExtensions :: General, enhancement, P2)

Description

[William Durand [:willdurand]]

See: https://developer.chrome.com/docs/extensions/reference/scripting/#type-ExecutionWorld

Comment 1

[William Durand [:willdurand]]

Unassigned myself because this is not a high priority bug for now.

Comment 2

[Rob Wu [:robwu]]

"ISOLATED" was supported in bug 1759932.
This bug is currently about supporting execution in the "MAIN" world (i.e. the web page).

Comment 3

[Rob Wu [:robwu]]

When we commence work on this, we should also create new bugs or patches to introduce support for world to scripting.registerContentScripts and content_scripts in manifest.json. Chromium implemented that in https://crbug.com/1330986

Comment 4

[Rob Wu [:robwu]]

The userScripts API proposal at https://github.com/w3c/webextensions/pull/331 includes the "USER_SCRIPT" world, after my feedback to the initial proposal. That is out of scope for this bug, we will file new bugs to implement the USER_SCRIPT world and new APIs when we get there (and these would be part of the userScripts namespace, not the scripting namespace anyway).

When this bug is fixed, we have to adjust the BCD that I added in https://github.com/mdn/browser-compat-data/pull/18878

Comment 5

[danielhunterjacobs]

I have worked on the Adobe Flash Player emulator Ruffle. There are a few things we've had to do differently between Firefox and Chromium to make sure it works on both browsers, and this is the cause of one of them.

On Chromium browsers, we are able to use scripting.registerContentScripts with the MAIN execution world to run a script (https://github.com/ruffle-rs/ruffle/blob/feacbdc118c92ff30f686c1203c6f08ccd92833d/web/packages/core/src/plugin-polyfill.ts#L203) to add "Shockwave Flash" to navigator.plugins to fool Flash detection scripts. The faster the script is run, the more likely it is to run before any Flash detection scripts. On Firefox, we instead have to add a raw script tag with the compiled form of that script as its source to do the same thing, which isn't as fast so is more likely to run after the detection already fails and is also a bit more roundabout.

Comment 6

[danielhunterjacobs]

This is the code we use on chromium: https://github.com/ruffle-rs/ruffle/blob/feacbdc118c92ff30f686c1203c6f08ccd92833d/web/packages/extension/src/background.ts#L12-L30

Comment 7

[Gregory Pappas [:gregp]]

On Firefox, we instead have to add a raw script tag with the compiled form of that script as its source to do the same thing

Hi Daniel, that shouldn't be necessary. See Sharing objects with page scripts.

Comment 8

[danielhunterjacobs]

(In reply to Gregory Pappas [:gregp] from comment #7)

On Firefox, we instead have to add a raw script tag with the compiled form of that script as its source to do the same thing

Hi Daniel, that shouldn't be necessary. See Sharing objects with page scripts.

That doesn't allow for running the script quickly enough that it can add "Shockwave Flash" to navigator.plugins before inline scripts on the page check for and don't see the presence of Shockwave Flash in navigator.plugins.