chrome.webRequest.onBeforeRequest not getting triggered when chrome.exe is launched with --disable-extensions-file-access-check

[Ashish Shivhare]

In my extension, I wanna do some logging with all file:\\ protocol urls & don't want to let user deselect "Allow file urls" check box for extension.

So, I launched chrome with flag : --disable-extensions-file-access-check 

But when chrome is launched, i am seeing onBeforeRequest event is not at all getting triggered.

I have mentioned file:\\ in manifest file as well.

Any ideas why the event is not getting triggered ?

[PhistucK]

Just to clarify -

Without the flag but with the file:// access check box ticked (so file:// access is enabled by the user) - you do get onBeforeRequest, right?

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chromium-Extensions-Announce" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.
To post to this group, send email to chromium-extensions@chromium.org.
Visit this group at https://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/a8bcad53-4dc7-443c-bb97-71076b534ac4%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[Ashish Shivhare]

Yes, It works fine without that flag.

But I want to use file:\\\ urls with that flag turned on.

On Wednesday, November 30, 2016 at 2:17:24 AM UTC+5:30, PhistucK wrote:

Just to clarify -

Without the flag but with the file:// access check box ticked (so file:// access is enabled by the user) - you do get onBeforeRequest, right?

☆PhistucK

On Tue, Nov 29, 2016 at 7:59 PM, Ashish Shivhare <ashish...@gmail.com> wrote:

In my extension, I wanna do some logging with all file:\\ protocol urls & don't want to let user deselect "Allow file urls" check box for extension.

So, I launched chrome with flag : --disable-extensions-file-access-check 

But when chrome is launched, i am seeing onBeforeRequest event is not at all getting triggered.

I have mentioned file:\\ in manifest file as well.

Any ideas why the event is not getting triggered ?

--
You received this message because you are subscribed to the Google Groups "Chromium-Extensions-Announce" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.

To post to this group, send email to chromium-...@chromium.org.

[PhistucK]

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged faster.

Do keep in mind that this is a very low priority issue, since using flags is not really supported.

Thank you.

☆PhistucK

On Wed, Nov 30, 2016 at 5:50 AM, Ashish Shivhare <ashish...@gmail.com> wrote:

Yes, It works fine without that flag.

But I want to use file:\\\ urls with that flag turned on.

On Wednesday, November 30, 2016 at 2:17:24 AM UTC+5:30, PhistucK wrote:

Just to clarify -

Without the flag but with the file:// access check box ticked (so file:// access is enabled by the user) - you do get onBeforeRequest, right?

☆PhistucK

On Tue, Nov 29, 2016 at 7:59 PM, Ashish Shivhare <ashish...@gmail.com> wrote:

In my extension, I wanna do some logging with all file:\\ protocol urls & don't want to let user deselect "Allow file urls" check box for extension.

So, I launched chrome with flag : --disable-extensions-file-access-check 

But when chrome is launched, i am seeing onBeforeRequest event is not at all getting triggered.

I have mentioned file:\\ in manifest file as well.

Any ideas why the event is not getting triggered ?

--
You received this message because you are subscribed to the Google Groups "Chromium-Extensions-Announce" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsubscribe...@chromium.org.

To post to this group, send email to chromium-...@chromium.org.
Visit this group at https://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/a8bcad53-4dc7-443c-bb97-71076b534ac4%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

--
You received this message because you are subscribed to the Google Groups "Chromium-Extensions-Announce" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.

To post to this group, send email to chromium-extensions@chromium.org.

Visit this group at https://groups.google.com/a/chromium.org/group/chromium-extensions/.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/88ca1516-2b72-4e07-a87e-91b31debc5f6%40chromium.org.