On Wed, Jul 29, 2009 at 11:39 PM, Peter Kasting <[email protected]>wrote:
> On Wed, Jul 29, 2009 at 9:18 PM, Tim Steele <[email protected]> wrote: > >> I've done something like this in the past, and it used to be that if I >> selected the second suggestion (which was *not* a "Search Google for: >> ..." type suggestion, it would actually go to my registered URL and from >> that point on this became the default whenever I typed a URL with my scheme. > > > Sorry, but that has never been the behavior. > > Navigation (rather than search) could become the default action for _that > URL_, but not for the entire scheme-- the autocomplete system doesn't learn > that way. > Im describing what the behavior I saw was; not claiming to know how the internals work. Sorry for the confusion. We only had one URL for the scheme in question, so whether it was for the entire scheme didn't matter. At first we didn't even notice the option below "Search Google for: .. " and assumed our scheme wasn't getting registered, so I suggested it in case something similar was going on here. Thanks for clarifying though! > > >> I'm trying to remember which piece of code I traced this to.. I'll take >> a look and reply if I can find it. > > > Probably things like AutocompleteInput::Parse() and the various results the > AutocompleteProviders returned. That's all higher-level than the desired > effect here, which needs to happen down in the scheme handling code. > > PK > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
