My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 153245: Docs need to clarify when you can use which schemes with match patterns.
12 people starred this issue and may be notified of changes. Back to list
 
Reported by kdzwinel@gmail.com, Oct 1, 2012
Chrome Version       : 22.0.1229.79
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)

What steps will reproduce the problem?
1. Create an extension that tries to inject content script to "chrome-extension://*/*"

What is the expected result?
According to documentation, script should be injected (http://developer.chrome.com/extensions/match_patterns.html). "chrome-extension://*/*" is listed as a valid pattern.

What happens instead?
Error is displayed when trying to enable extension: "Invalid value for 'content_scripts[0].matches[0]': Invalid scheme."

Please provide any additional information below. Attach a screenshot if
possible.

It's also not possible to use "chrome-extension://*/*" in "permissions" attribute of manifest file.

UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.79 Safari/537.4


Oct 25, 2012
#1 david.pr...@gmail.com
Confirmed for me (24.0.1305.3 (Versão oficial 163672) dev-m).
Oct 26, 2012
#2 manoranj...@chromium.org
kdzwinel@, Could you please provide us with any specific Extension that will inject content script to "chrome-extension://*/*" pattern? so that it will be easy for us to reproduce this issue.

Thanks,
Mano


Cc: manoranj...@chromium.org
Labels: Action-FeedbackNeeded
Oct 26, 2012
#3 david.pr...@gmail.com
@manoranj No one extension. Extensions can't match it currently, you will get a error like @kdzwinel told.


---------------------------
Extension error
---------------------------
Could not load extension from '[...]/match-issue'. 
Invalid value for 'content_scripts[0].matches[0]': Invalid scheme.
--> Ref. to: "matches": [ "chrome-extension://*/*" ]


I attached an example extension.
match-issue.rar
303 bytes   Download
Oct 26, 2012
#4 manoranj...@chromium.org
I am able to REPRODUCE this issue and is existing from M#21 onwards on Win7. I have tested the other pattern "http://*/* (which is there in http://developer.chrome.com/extensions/match_patterns.html) and it is working fine with out any issues.

Thanks,
Mano
Status: Untriaged
Labels: -Action-FeedbackNeeded Feature-Extensions
Oct 26, 2012
#5 ligim...@chromium.org
(No comment was entered for this change.)
Labels: -Area-Undefined Area-UI Mstone-22
Oct 31, 2012
#6 a...@chromium.org
This is intended behavior; the docs are just wrong. You aren't meant to be able to inject content scripts into other extensions.

Meggin, we should make this more clear. chrome-extension is only allowed in some cases with match patterns.
Summary: Docs need to clarify when you can use which schemes with match patterns.
Status: Assigned
Owner: mkear...@chromium.org
Labels: -Type-Bug -OS-Windows -Mstone-22 Type-Documentation OS-All
Oct 31, 2012
#7 a...@chromium.org
(No comment was entered for this change.)
Labels: -Area-UI Area-Internals
Mar 9, 2013
#8 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Type-Documentation -Area-Internals -Feature-Extensions Cr-Platform-Extensions Documentation Cr-Internals Type-Bug
Oct 22, 2013
#9 m...@google.com
It's been a year since this was first raised, and the docs are still achingly misleading.  I just lost a significant amount of time re-engineering some code based on this faulty documentation.  This should be a pretty easy fix, and it's pretty important to content script developers.
Oct 23, 2013
#10 binji@chromium.org
Agreed, I had the same problem. I'm happy to make the doc change if someone can tell me in which cases the "chrome-extension" scheme is valid.
Oct 23, 2013
#11 binji@chromium.org
(No comment was entered for this change.)
Cc: binji@chromium.org
Feb 11, 2014
#12 MetalMep...@gmail.com
I had the same problem as well. I would really like to know when "chrome-extension://*" is valid for content scripts. The note in the docs currently says: 

"Some schemes are not supported in all contexts" 

... which is not very helpful. I just wasted several hours trying to debug something related to this before I deduced that my context is one of those unsupported.

For what it's worth, I can understand not being allowed to access any extension. However, matching your own extension paths seems reasonable (to me), and would save me a lot of headache. I know there are others with the same need.
Jul 21, 2014
#14 christop...@gmx.com
Me, too, I just wasted my time on this.
October 2012... Man. Get things going already or you'll piss of even more extension devs.
Sign in to add a comment

Powered by Google Project Hosting