We had considered doing this early on, but the problem is that no sites
actually own all of the eTLDs for their name, and most sites only own a
small percentage of the available.  Worse than that, the ones that aren't
owned by the company are often phishing sites or worse.  These are not the
sites you want to be injecting into accidentally.

I can understand that with Google in particular, it would be nice to be able
to say "all google sites".  Unfortunately, there isn't a good and safe way
to do this without listing out all of the domains manually.

Erik


On Wed, Dec 16, 2009 at 11:47 AM, Ben <[email protected]> wrote:

> I'm developing a couple of extensions and I've come across that you
> cannot use a wildcard in a domain unless it's at the start.
> What I'd like to be able to do is, for example:
>
> "content_scripts": [
>  { "matches": ["http://images.google.*/*";]
>   "js": ["myscript.js"]
>  }
>
> Either a wildcard that can be entered at the end of a domain, or a
> different wildcard that supports all TLDs.
> I remember seeing some kind of feature like this somewhere.
>
> Maybe something like:
>
> "content_scripts": [
>  { "matches": ["http://images.google.#TLD#/*";]
>   "js": ["myscript.js"]
>  }
>
> Does anybody know of an existing feature like this or is it feasible
> to have it added to a nightly build?
>
> Thanks,
> Ben
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Chromium-extensions" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<chromium-extensions%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/chromium-extensions?hl=en.
>
>
>

--

You received this message because you are subscribed to the Google Groups 
"Chromium-extensions" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/chromium-extensions?hl=en.


Reply via email to