Multiple content-script not working

[imagents]

Version

6.0.1

Current Behavior

If you inject multiple content-script into a page with the first one declare onMessage('A) and the second one with no onMessage declaration. When you sendMessage from background. The background will throw an error "No handler registered in 'content-script' to accept messages with A".
However if you switch the first one and second one position in manifest. It works.

Expected Behavior

Both onMessage declared in content-script will work.

Steps To Reproduce

Just create two content-script and inject into the same page

Anything else?

No response

[SaschaLucius]

I face the same problem when using WXT with webext-bridge.

If I define two content scripts and try to message between them, I always get:
Error sending xxxxx message: Error: [webext-bridge] No handler registered in 'content-script' to accept messages with id 'xxxxx'

[chengyong4010]

I’m encountering the same issue, and it’s causing significant troubleshooting difficulties.

[seahindeniz]

As a workaround (not the best one), creating a gateway script that provides bridge methods under Window object. Since it get injected only single time, the port works as expected.

messageGateway, must be added to manifest as content_scripts's first item.

import { onMessage, sendMessage } from 'webext-bridge/content-script'

window.messageGateway = {
  sendMessage,
  onMessage,
}

contentScript1

const res = await window.messageGateway.sendMessage('get-details');

console.log(res);

contentScript2

window.messageGateway.onMessage('hello', ({ data }) => {
  console.log(data);
});

manifest

{
  "content_scripts": [
    {
      "matches": [
        "<all_urls>"
      ],
      "js": [
        "contentScripts/messageGateway.js"
      ]
    },
    {
      "matches": [
        "<all_urls>"
      ],
      "js": [
        "contentScripts/contentScript1.js"
      ]
    },
    {
      "matches": [
        "<all_urls>"
      ],
      "js": [
        "contentScripts/contentScript2.js"
      ]
    },
  ]
}

I haven't tested this on "world": "MAIN"or with different run_at, so I'm not sure how it would effect.