Index: chrome/browser/chromeos/chrome_browser_main_chromeos.cc |
diff --git a/chrome/browser/chromeos/chrome_browser_main_chromeos.cc b/chrome/browser/chromeos/chrome_browser_main_chromeos.cc |
index 28664f9dcc4454d835eec2cb46cd884ab86eb6ef..b63c56c2293cf662569ff8a8c9351ea72555b338 100644 |
--- a/chrome/browser/chromeos/chrome_browser_main_chromeos.cc |
+++ b/chrome/browser/chromeos/chrome_browser_main_chromeos.cc |
@@ -350,6 +350,10 @@ void ChromeBrowserMainPartsChromeos::PreProfileInit() { |
// -- This used to be in ChromeBrowserMainParts::PreMainMessageLoopRun() |
// -- immediately before Profile creation(). |
+ // In Aura builds this will initialize ash::Shell. Call it first so that |
+ // the device scale factor is available when loading images. |
oshima
2012/10/10 16:21:28
// Call it first before performing UI related task
stevenjb
2012/10/10 17:07:27
How this initializes Ash is not entirely obvious,
|
+ ChromeBrowserMainPartsLinux::PreProfileInit(); |
+ |
// Now that the file thread exists we can record our stats. |
chromeos::BootTimesLoader::Get()->RecordChromeMainStats(); |
stevenjb
2012/10/10 17:07:27
This should probably still be first.
|
@@ -405,9 +409,6 @@ void ChromeBrowserMainPartsChromeos::PreProfileInit() { |
} |
chromeos::UserManager::Get()->SessionStarted(); |
} |
- |
- // In Aura builds this will initialize ash::Shell. |
- ChromeBrowserMainPartsLinux::PreProfileInit(); |
} |
void ChromeBrowserMainPartsChromeos::PostProfileInit() { |