I'm not aware of any MV3 changes with respect to file:// permissions
@DotProto FYI, following the regression in SingleFileZ and its future with MV3 restrictions, an issue has been created here https://bugs.chromium.org/p/chromium/issues/detail?id=1051597 …. Maybe you'll be able to answer to this question: What is the purpose of the host permission "file://*/*" in the manifest V3?
-
-
-
With MV3, content scripts won't be allowed to do a XHR on file://. In the service worker, XHR is not present and fetch is not allowed to read a file:// URI (cf. the spec.). To sum up, I don't see how the "file://" host permission can be used with MV3.
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.