We chose not to have a .tld or similar in content scripts because most large websites still don't have every single version of their domain name. For example there are many google.* domains that aren't Google.
You can match http://*/* and just check for Google in the host manually. I'll create a bug to reconsider the .tld thing. - a On Mon, Jun 1, 2009 at 1:23 AM, Patrick Stenzel <[email protected]> wrote: > > Hi, > > i`m currently writing a port of a firefox-extension, which extends the > searchresults delivered by google. > The used content script should of course be executed only on google- > pages and i did that using the match patterns described here: > http://dev.chromium.org/developers/design-documents/extensions/match-patterns > The problem is, i don`t want to (and probably can not) insert a > pattern for every single localized version of google, but the system > does not accept wildcars in the TLD-area of the host definition. > > A definition of "http://*.google.*/*"; quits qith an error. Is this a > bug? Did i do something wrong? > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
