@DotProto Once again Chrome 80 introduced a regression that breaks one of my extensions (SingleFileZ).
Is it intentional that content scripts can't make XHR on the file URL of the displayed page anymore (with the <all_urls> permission)?
Forcing users to launch Chrome with the switch "--allow-file-access-from-file" is not acceptable from my point of view. I'll probably unpublish the extension if this regression is not fixed.
-
-
I was able to circumvent this regression by doing the XHR to the file URI in the background script. If you can make anything to make the fix available more quickly than usual, that would be helpful and would show Google can assume regressions introduced in Chrome.
Show this thread -
@DotProto Sorry to have bothered you, I thought you were Developer Advocate for@ChromiumDev Extensions.Show this thread
End of conversation
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.