Chromium Code Reviews| Index: chrome/browser/chrome_content_browser_client.cc |
| diff --git a/chrome/browser/chrome_content_browser_client.cc b/chrome/browser/chrome_content_browser_client.cc |
| index a0ad854e231c6296469b8ee2a44639cf5c3b6ea8..135e9db519dd3336585c110c154ade76e14a7b2e 100644 |
| --- a/chrome/browser/chrome_content_browser_client.cc |
| +++ b/chrome/browser/chrome_content_browser_client.cc |
| @@ -104,6 +104,7 @@ |
| #include "components/pref_registry/pref_registry_syncable.h" |
| #include "components/signin/core/common/profile_management_switches.h" |
| #include "components/translate/core/common/translate_switches.h" |
| +#include "components/url_fixer/url_fixer.h" |
| #include "content/public/browser/browser_child_process_host.h" |
| #include "content/public/browser/browser_main_parts.h" |
| #include "content/public/browser/browser_ppapi_host.h" |
| @@ -2261,7 +2262,8 @@ void ChromeContentBrowserClient::BrowserURLHandlerCreated( |
| // about: handler. Must come before chrome: handler, since it will |
| // rewrite about: urls to chrome: URLs and then expect chrome: to |
| - // actually handle them. |
| + // actually handle them. Also relies on a preliminary fixup phase. |
| + handler->SetFixupHandler(&FixupBrowserAboutURL); |
|
msw
2015/02/18 22:01:23
Is it reasonable to just call AddHandlerPair with
Charlie Reis
2015/02/18 22:16:17
I don't think so, since all the handlers added by
|
| handler->AddHandlerPair(&WillHandleBrowserAboutURL, |
| BrowserURLHandler::null_handler()); |