diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-12-20 21:46:38 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-12-20 21:46:38 +0000 |
| commit | 83d4ccb31ecee09ced4c6d7e7e51011e876d5399 (patch) | |
| tree | e6913ce6baa10b25d8f079650005d0bcab4f704b /chrome/browser/chrome_browser_main.cc | |
| parent | 8a0bd531f07b5d8f5f9b4307ef4b0a75eb5b69ab (diff) | |
| download | chromium_src-83d4ccb31ecee09ced4c6d7e7e51011e876d5399.zip chromium_src-83d4ccb31ecee09ced4c6d7e7e51011e876d5399.tar.gz chromium_src-83d4ccb31ecee09ced4c6d7e7e51011e876d5399.tar.bz2 | |
Initialize high dpi early in the chrome process on Windows by calling the SetProcessDpiAware API in chrome.exe instead of chrome.dll
This API needs to be invoked as early as possible in the process. Not doing this causes the OS to assume that the process
needs dpi scaling which leads to bad things. We also need to initialize high dpi in the gpu process as it is involved in win32
operations like painting, etc.
BUG=330093
R=cpu@chromium.org
TBR=sky
Review URL: https://codereview.chromium.org/100923011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@242182 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/chrome_browser_main.cc')
| -rw-r--r-- | chrome/browser/chrome_browser_main.cc | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/chrome/browser/chrome_browser_main.cc b/chrome/browser/chrome_browser_main.cc index ed8eb92..4abe27f 100644 --- a/chrome/browser/chrome_browser_main.cc +++ b/chrome/browser/chrome_browser_main.cc @@ -892,10 +892,6 @@ int ChromeBrowserMainParts::PreCreateThreadsImpl() { const std::string locale = local_state_->GetString(prefs::kApplicationLocale); -#if defined(OS_WIN) - gfx::EnableHighDPISupport(); -#endif - // On a POSIX OS other than ChromeOS, the parameter that is passed to the // method InitSharedInstance is ignored. |