Using Chrome:// links from the extension's popup.

[Bogdan Nazaruk]

Hey! I just have this thing in the popup:

<a href="chrome://flags/#enable-force-dark" target="_blank">Chrome Flags</a>

And it doesn't work. 

The error is confusing. It says: Not allowed to load local resource: chrome://flags/#enable-force-dark

But I'm not trying to load resources from there. I just want users to open the flags page conveniently.

No way to do that? I'll just have to allow them to copy it and paste it manually?

[woxxom]

It's a misleading error message, but the behavior is intended: this scheme is privileged and doesn't allow navigation via links from non-chrome pages. You can make a feature request in https://crbug.com because extensions can do it explicitly via API anyway in a click listener for the link: chrome.tabs.create({url: 'chrome://flags/#enable-force-dark'})

[Bogdan Nazaruk]

Wooooow. Yep, I just used your hack and it works perfectly fine. Thank you very much for sharing. I'm not gonna bother submitting a request though. I really doubt they pay much attention to them. I submitted quite a few by now via Chrome -> Help -> Report an Issue, but got no response.

[Patrick Kettner]

Thanks woxxom!

We do pay attention to the reports (we reach literally every single one), we just don't really have a good way of responding currently. If you don't open an issue for it, im more than happy to on your behalf (its how features are organized and prioritized for implementation).

best

patrick

--
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/9e992fbe-03cd-4cbc-b226-d58905d5815cn%40chromium.org.

[Bogdan Nazaruk]

When we report an issue, there's a field to capture our email. I would call that email a very good way to receive feedback. What I thought happened is a ticker would be created, using the email provided as a watcher, so every response to that ticket would result in an email to the initiator. 

I would create a ticket if I knew where to do that, but this article omits any indication of how to submit tickets properly: https://support.google.com/chrome/answer/95315?hl=en&co=GENIE.Platform%3DDesktop Which makes me think Chrome devs actually actively don't want us to create any tickets anywhere else.

[Patrick Kettner]

> When we report an issue, there's a field to capture our email. I would call that email a very good way to receive feedback. 

for sure! But from the eng side of things, there isn't' a mechanism by which we can respond. The email isn't shared with the information being reviewed, for privacy reasons. I am not defending the current situation, I agree with your feeling on it, I just want to explain a bit about it.

> I would create a ticket if I knew where to do that

crbug.com/new 

best

patrick