Make it possible to launch chrome --mash with ozone_platform={wayland|x11}, chromeos=0

chrome/browser/ui/browser_view_prefs.cc

Index: chrome/browser/ui/browser_view_prefs.cc
diff --git a/chrome/browser/ui/browser_view_prefs.cc b/chrome/browser/ui/browser_view_prefs.cc
index 1bf1eb74b2a0b8088abd6e609a39de9e131b9f1d..272ffc24dad7ad5fbc1daa85b65320bb3025abfb 100644
--- a/chrome/browser/ui/browser_view_prefs.cc
+++ b/chrome/browser/ui/browser_view_prefs.cc
@@ -32,7 +32,7 @@ void RegisterBrowserViewLocalPrefs(PrefRegistrySimple* registry) {
 
 void RegisterBrowserViewProfilePrefs(
     user_prefs::PrefRegistrySyncable* registry) {
-#if defined(OS_LINUX) && !defined(OS_CHROMEOS)
+#if defined(OS_LINUX) && !defined(OS_CHROMEOS) && !defined(USE_OZONE)

[Tom (Use chromium acct), 2016/10/17 23:40:52]

why is this needed?

[tonikitoo, 2016/10/18 04:55:06]

This is needed because ui::GetCustomFramePrefDefault (from ui/base/x/x11_util.cc
| h) is only built for use_x11 or wayland_platform_x11 builds.

Ideally, there should be a ui/base/ozone/ozone_util.cc implementing this
function, but for this bring-up, I decided to simple ifdef it out. Maybe a TODO
would be enough for now?

Note that CHROMEOS builds, even when running with ozone/x11, do not run this
method.

   registry->RegisterBooleanPref(prefs::kUseCustomChromeFrame,
                                 ui::GetCustomFramePrefDefault());
 #endif