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.
+    { "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 all the other URLs have
one...

[Jered, 2013/08/14 15:41:49]

Hrm I'm not sure. I don't anticipate ever wanting to post data to the ntp. Peter
do we need this for some reason?

     // 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" }
   ]
 }