Re: Chrome extension doesn't work for local URL's

[Cuyler Stuwe]

Did you try turning on this setting after installing the CWS copy?

On Thursday, June 15, 2023 at 2:29:20 PM UTC-7 Menno Veerkamp wrote:

My extension specifically works for PDF files in the browser. The intention is for the extension to work for any URL and then check within the extension whether the URL ends with ".pdf" so that the brightness of that page can be adjusted.

The extension works for every PDF file in development, but the web store version only works for HTTP(S) links and not for file:/// links. I assume this is related to security. I'm not sure if I missed something during testing of the extension or if there have been recent changes regarding extension security, but i would like for the extension to work for any URL.

For the use of my extension, access to the data on the screen is not required, only access to the URL. Is there a way to make the extension work for file:/// URLs as well?

 

[Patrick Kettner]

yes

On Fri, Jun 16, 2023 at 6:13 AM Menno Veerkamp <veerka...@gmail.com> wrote:

That did the trick, thanks! I assume this has to be manually done by every user installing the extension to make it work for every URL? 

Op vrijdag 16 juni 2023 om 02:01:26 UTC+2 schreef Cuyler Stuwe:

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/75cc76db-a8f3-4e8d-a8b3-b6fc7694ce83n%40chromium.org.

[Mitchell]

Perhaps you can detrct if you have the appropriate permission with extension.isAllowedFileSchemeAccess() and prompt the user to take the required action.