Content script injection inconsistencies in the sidePanel

[grahamlangford]

Context

• The behavior of content script injection in side panels is inconsistent between Chrome and Edge

  • In Chrome, the extension's content script is automatically injected

    

  • In Edge, the extension's content script is not injected

    

Related Discussions

• https://github.com/pixiebrix/pixiebrix-extension/issues/8206#issuecomment-2115232943

[twschiller]

For reference, the manifest for the content script is:

    {
      "matches": ["*://*/*"],
      "exclude_matches": ["https://*.googleapis.com/*"],
      "js": ["contentScript.js"],
      "css": ["contentScript.css"],
      "all_frames": true,
      "match_about_blank": true,
      "run_at": "document_idle"
    },

In the sidebar, we need to iframe some 3rd party content. The structure we use is:

• Top: our extension side panel page
  • frame.html: A shim extension frame around the 3rd party frame (adjusting some CSP, etc.)
  • The 3rd party frame (which itself might have iframes)

Our assumption is the expected behavior is the Chrome behavior - that the content script is injected into frames within the sidebar?

[tophf]

Might be helpful to clarify that you mean the extension's own content script and indeed you and Chrome are correct here because how else the extension would be able to scrape a web site embedded in its page?