search engine not default and new tab extension

[Jean Lomdes]

Hi,

I am creating a new tab extension.

I read about the new Chrome policy that requires to use chrome.search api if the extension includes a web search. Did I understand the policy correctly? 

I would like my new tab extension to include a new search engine, so it is added to list of search engine available in settings. I understand to not be in conflict with single purpose policy, my extension cannot change the default search engine, so I set it to default: false like that 

  "chrome_settings_overrides": {
    "search_provider": {
      "encoding": "UTF-8",
      "favicon_url": "https://somesearchengine.com/favicon.png",
      "name": "Some search engine",
      "is_default": false,
      "keyword": "ssg",
      "search_url": "https://somesearchengine.com/search/?q={searchTerms}"
    }
  },

So now, I load the extension in developer mode but the new search engine is not listed in chrome://settings/searchEngines. Why? 

My goal here is not let the user choose this new search engine in settings if that is his/her wish and use chrome.search API for the web search box of my extension.

Thank you,

Jean

[Jean Lomdes]

Realized the search engine shows up in Site search which does not help in my case, since it can't be used as default search later on. Weird concept.