1797943 - Matching first on HTTP, then on HTTPS, prevents a content script from activating

Status: RESOLVED DUPLICATE of bug 1778461

(WebExtensions :: General, defect)

Description

[Vincent]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0

Steps to reproduce:

I created a Manifest V3 add-on, that I wanted to be active on all HTTP sites. Thus, I added a content script with the following matches value:

  "matches": ["http://*/*", "https://*/*"],

(The problem does not occur if HTTPS is listed first.)

I've created a reproduction at https://gitlab.com/bug-repros/firefox-mv3

You can verify the bug in that repository; reverting commit bed4713287dacdb8c4eb8e106728926e02c9a24f makes it work again.

Actual results:

Even after giving my add-on permission to inject via about:addons, the content script did not activate.

(And I believe web_accessible_resources have the same problem.)

Expected results:

The content script should be injected.

Comment 1

[Rob Wu [:robwu]]

Thanks for the very clear reproduction steps. It was reported before, but not as clear as your test case, at bug 1778461.