Hi, if i redirect to the .com i`d have to check the host myself and if i do so i can take aaron`s solution as well.
On 1 Jun., 16:37, Mohamed Mansour <[email protected]> wrote: > Hi for now, can't you place .com and make sure your extension redirects to a > dot com? If the user in a localized area seen a dot come it will direct him > to the proper locale. For example, I visit google.com it will redirect me to > google.ca. Therefore, you can place your pattern as google.com > > -- Mohamed Mansour > > On Mon, Jun 1, 2009 at 4: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-... > > 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 -~----------~----~----~----~------~----~------~--~---
