InstantExtended: Add new_tab_url to TemplateURL.

chrome/browser/search_engines/prepopulated_engines_schema.json

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.

[Peter Kasting, 2013/08/14 23:21:45]

Nit: Move this above the post_params fields (and in the other .json file too)

We could also try and distribute these fields amongst the other fields above,
but that would imply we should reorder things over in TemplateURL too, which
would be kind of a mess, I think.  But maybe that'd be better.

[Jered, 2013/08/15 16:44:03]

Done. I don't have a preference about interleaving or splitting the sub-fields,
so I'll go with the smaller diff.

+    { "field": "new_tab_url", "type": "string", "optional": true },
     // 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