InstantExtended: Committed NTP

content/public/common/url_constants.h

Index: content/public/common/url_constants.h
diff --git a/content/public/common/url_constants.h b/content/public/common/url_constants.h
index 19c31cf45d26ed2c89ce1afe16627e034bdbba95..bee2c960404b1fb958e12c97689fa7628396b475 100644
--- a/content/public/common/url_constants.h
+++ b/content/public/common/url_constants.h
@@ -56,6 +56,7 @@ CONTENT_EXPORT extern const char kChromeUIGpuCrashURL[];
 CONTENT_EXPORT extern const char kChromeUIGpuHangURL[];
 CONTENT_EXPORT extern const char kChromeUIHangURL[];
 CONTENT_EXPORT extern const char kChromeUIKillURL[];
+CONTENT_EXPORT extern const char kChromeUINewTabURL[];

[jam, 2013/01/29 17:51:55]

content layer should not know about chrome layer's features, i.e. new tab page

[samarth, 2013/01/31 16:24:57]

Do you have other suggestions for how best to communicate to the content layer
that a particular contents should have FocusLocationBarByDefault() set to true?
Some options:

(1) Add some explicit API that chrome/ code can call on a web contents to set
FocusLocationBarByDefault(true)
(2) Add another channel for communicating this bit?  (Similar to how it's done
right now with webui but a new one since we don't have a webui in this case
anymore.)
(3) Don't do it content/ at all and just try to cover all the cases on the
chrome side.  It may be possible but it would definitely be more bug-prone.
(4) Keep it like this. It's simplest and it's how we're currently handling
focus-by-default for about://blank.  Also it looks like there's already a bunch
of chrome-specific URLs in this list (e.g. ChromeUIAppCacheInternals,
ChromeUIDevTools, etc.)

 CONTENT_EXPORT extern const char kChromeUIPpapiFlashCrashURL[];
 CONTENT_EXPORT extern const char kChromeUIPpapiFlashHangURL[];