Missing a key difference: Firefox does CORS preflight request, Chrome doesn't about content HOT 3 CLOSED

Can you provide more details about the inconsistencies you observed? I put together a test CORS extension and ran it in both Chrome and Firefox. I also tested with host permissions both granted and restricted. In my tests I did not observe any inconsistencies between the preflight behavior of either browser. All tests were performed on macOS 14.4.1.

At the moment my best guess is that your are developing a Manifest V3 extension and have not manually granted the extension it's requested host permissions. Firefox's current design restricts host permission grants for Manifest V3 extensions at install time. There are a couple of relevant issues on Bugzilla related to this such as
1770698 and 1839129.

from content.

@dotproto it's easy enough to replicate, but before I spend time to put together a demo extension for you to replicate, can you confirm whether this is by design? I run into CORS only when making requests from the options page, but it works fine from background page. If this is by design, then we can close this.

P.S. In Chrome/Edge the same requests work fine on options page as well.

from content.

I'm closing this since I just created a minimal extension and was not able to reproduce the issue again.

from content.