opensearch.xml config not added to search engine settings immediately
Reported by
bradley....@gmail.com,
Apr 5 2017
|
|||
Issue descriptionSteps to reproduce the problem: 1. Navigate to a homepage that has an opensearch.xml document e.g. https://duckduckgo.com. 2. Go to settings > search engine 3. Observe that duckduckgo.com is not in the list. What is the expected behavior? After multiple searches it eventually shows up in the settings > search engine menu list as an option. The opensearch file should be parsed on the initial homepage visit and the website in question listed as a search engine option. Desktop does this. What went wrong? The search engine wasn't listed as an option upon the initial homepage visit, as it does with desktop. Did this work before? No Chrome version: 59.0.3056.4 Channel: n/a OS Version: 7.1.1 Flash Version:
,
Apr 6 2017
,
Apr 6 2017
This is designed behavior. We surface the most recently used engine(s) as options to set-as-default. Searching once should be enough to put this in the list. On desktop, we have the UI space to show all detected engines for sites you've visited, so we do so, but on Android we have to use some kind of limiting heuristic. tedchoc: Feel free to yowl if we should rethink the decision to base exposure on recent use rather than "recently visited a page that referenced this". |
|||
►
Sign in to add a comment |
|||
Comment 1 by candr...@chromium.org
, Apr 6 2017Components: UI>Browser>Omnibox>TabToSearch
Status: Available (was: Unconfirmed)