Let content-script work on chrome-extension:// urls
Reported by
a1032453...@gmail.com,
May 21 2018
|
|||||
Issue descriptionI'm poor in English, so I need a translate extension help me comprehend the English sites. The extension will translate some difficult word and highlight or tag the difficult words on the page. And I had developed it. This translate extension is work good in the online sites. However, when I try to read an EPUB format English textbook in the local file system by using a called EPUBReader extension but my translate extension didn't work in the EPUBReader extension page anymore. I had read the "Can extensions modify chrome:// URLs?" at the help page which say it is not stable to let extension word on chrome:// pages. But I had seen Experiments flag called "Extensions on chrome:// URLs" in the "chrome://flags/" page, why could you add the similar Experiments flag like "Extensions on chrome-extension:// URLs" in the "chrome://flags/" page? I readily need this function then my extension can work everywhere and it could help me improve my English.
,
May 21 2018
This feature was suggested and rejected multiple times: bug 77440 , bug 17981 , bug 124004 , bug 390034 , bug 176032 . Judging by the rejections, implementing it securely is either impossible or requires too much effort in order to isolate the injected content script and prevent them from gaining access to the API available in the host extension page.
,
May 21 2018
,
May 22 2018
Thanks for filing the issue! Considering this as a feature request and making the status to Untriaged so that the issue would get addressed. Could some one from Extensions dev team please look in to this issue. Thank you!
,
May 25 2018
[Extensions Triage] Closing this since we don't allow extensions to inject scripts into other extension pages by design.
,
May 25 2018
As woxxom@ and karandeepb@ mentioned, this isn't something we want by default for various reasons. That said, I'm pretty sure the "Extensions on chrome:// urls" flag actually allows extensions on both chrome:// urls and chrome-extension:// urls. Have you tried enabling that flag and seeing what happens? (Note: features in chrome://flags are not fully supported, and are subject to change or removal at pretty much any time. This particular one has some pretty good use cases, just like this, though, so it may be sticking around) |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by a1032453...@gmail.com
, May 21 2018191 KB
191 KB View Download