@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?
-
-
Replying to @check_ca
I'm not aware of any MV3 changes with respect to file:// permissions
1 reply 0 retweets 0 likes -
Replying to @DotProto
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.
1 reply 0 retweets 1 like -
Replying to @check_ca
"fetch is not allowed to read a file:// URI (cf. the spec.)." I didn't realize that. I'll start some conversations
1 reply 0 retweets 0 likes -
Replying to @DotProto
BTW, I also use URL.createObject when calling the http://chrome.downloads.download method to pass the user generated content (i.e. the saved page) and download it. URL.createObject is not present in the service worker, what should I do?
1 reply 0 retweets 1 like -
Replying to @check_ca
I was about to thank you for the discussion on http://crbug.com/1051597 . Keep doing what you're doing, namely reporting gaps that we overlooked or may have misunderstood. Wouldn't hurt to create a hotlist of those items
1 reply 0 retweets 1 like
Thank you! I'll do my best :)
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.