On Sat, Jul 6, 2024 at 1:20 AM Oliver Dunk <oliverd...@google.com> wrote: > Is there a possibility of using the file:// scheme here? I'm not familiar > enough with ChromeOS and the filesystem:// scheme to know if that would work, > but that scheme is supported in `fetch` and what we would expect to be used > most often.
Despite sounding similar, the file:// and filesystem:// schemes aren't completely interchangeable. Furthermore, our manifest.json's content_security_policy does not list file: (but it does list filesystem:) and, IIUC, opening up file: would let the extension e.g read the entire user profile directory. > For testing, note that you need to request the `file://*` host permission and > enable the "Allow access to file URLs" toggle on the extension's details page. The ChromeOS Image Loader extension is 'built into ChromeOS' and doesn't actually show in the chrome://extensions page. It's a private implementation detail of the OS UI (the file manager). Even if it did show, FWIW, on my other extensions, I don't see a "Allow access to file URLs" toggle on the details pages. Thanks anyway for the suggestions. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEdON6bVq%2BcFOafDtRJqv1zwDtKv%2B1-jNH8vwVcTGnrWoQY5zA%40mail.gmail.com.
