Index: chrome/browser/search_engines/prepopulated_engines_schema.json |
diff --git a/chrome/browser/search_engines/prepopulated_engines_schema.json b/chrome/browser/search_engines/prepopulated_engines_schema.json |
index 893e5656ae8b01c40b44257c90f46c060387a712..6a153a41085c2eecc6a681b3961b71325ce1b432 100644 |
--- a/chrome/browser/search_engines/prepopulated_engines_schema.json |
+++ b/chrome/browser/search_engines/prepopulated_engines_schema.json |
@@ -42,6 +42,8 @@ |
{ "field": "suggest_url_post_params", "type": "string", "optional": true }, |
{ "field": "instant_url_post_params", "type": "string", "optional": true }, |
{ "field": "image_url_post_params", "type": "string", "optional": true }, |
+ // If omitted, this engine does not support rendering a new tab page. |
+ { "field": "new_tab_url", "type": "string", "optional": true }, |
samarth
2013/08/13 23:47:59
I don't see a need for new_tab_url_post_params but
Jered
2013/08/14 15:41:49
Hrm I'm not sure. I don't anticipate ever wanting
|
// A list of URL patterns that can be used, in addition to |search_url|, |
// to extract search terms from a URL. |
// If "search_url_post_params" is not empty, then all alternate URLs are |