InstantExtended: Add new_tab_url to TemplateURL.

chrome/browser/search_engines/prepopulated_engines_schema.json

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // This file is used by json_to_struct.py to generate prepopulated_engine.h/cc.
 // Any time you modify this file regenerate the .h/.cc. See
 // prepopulated_engines.json for details.
 
 {
   "type_name": "PrepopulatedEngine",
@@ skipping 24 matching lines @@
     // pairs, e.g.:
     // "name1=value1,name2={template1},...".
     // In each name/value pair, the equal sign('=') must be delimiter between
     // name and value. In above example, the "value1" is the constant value for
     // "name1", which is not replaceable. The {template1} is a replaceable value
     // for name2, the actual value will be replaced with real search terms data.
     { "field": "search_url_post_params", "type": "string", "optional": true },
     { "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
     // sent using POST with using same post parameters as the search URL.
     {
       "field": "alternate_urls",
       "type": "array",
       "contents": { "type": "string" },
       "optional": true
     },
@@ skipping 25 matching lines @@
     // the future; in such a case the localized engines will transparently
     // replace the previous, non-localized versions.  For engines where we need
     // two instances to appear for one country (e.g. Bing Search U.S. English
     // and Spanish), we must use two different unique IDs (and different
     // keywords).
     //
     // See prepopulated_engines.json for the list of available IDs.
     { "field": "id", "type": "int" }
   ]
 }