Content Script matching chrome-extension://

[Rubel Rana]

Is it possible for content scripts to be injected in chrome-extension:// urls? Maybe if it's in a separate tab instead of popup you can inject with activeTab permission?

[Patrick Kettner]

Extensions don't have access to other extensions, and there would be no reason to inject a content script on your own page.

What are you wanting to accomplish?

On Thu, Feb 27, 2025 at 10:50 AM Rubel Rana <rubel...@gmail.com> wrote:

Is it possible for content scripts to be injected in chrome-extension:// urls? Maybe if it's in a separate tab instead of popup you can inject with activeTab permission?

--
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 visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/d8bc72d2-c715-48a4-808f-0d373c261f05n%40chromium.org.

[Patrick Kettner]

Is there a reason you have to inject a content script to do that? As opposed to opening a new tab explaining the situation?

On Thu, Feb 27, 2025 at 11:17 AM Rubel Rana <rubel...@gmail.com> wrote:

A functionality of my extension conflicts with couple other extensions' functionality, I was thinking disabling the options that causes the conflicts via script with user consent, but if there is no way I could just prompt user to disable it themselves.

[Patrick Kettner]

Right, but what you were asking for is not an option either. 

On Thu, Feb 27, 2025 at 11:27 AM Rubel Rana <rubel...@gmail.com> wrote:

Well I thought it would be more convenient for user to just click a button and the extension changing settings of the conflicting extension for them. Most users probably don't care to read or change the settings themselves. As I said if there's truly no way I'm gonna hope user will change it themselves.

[woxxom]

There's a special command line switch that grants access both to chrome:// and chrome-extension:// schemes, alternatively chrome.debugger API should work.

[Rubel Rana]

Well I thought it would be more convenient for user to just click a button and the extension changing settings of the conflicting extension for them. Most users probably don't care to read or change the settings themselves. As I said if there's truly no way I'm gonna hope user will change it themselves.

[Rubel Rana]

I wasn't sure if it was an option or not, so I came to ask here. I suppose there is no point in keeping the conversation, have a nice day.

[Rubel Rana]

A functionality of my extension conflicts with couple other extensions' functionality, I was thinking disabling the options that causes the conflicts via script with user consent, but if there is no way I could just prompt user to disable it themselves.

On Thursday, February 27, 2025 at 9:59:43 PM UTC+3 Patrick Kettner wrote: