Use float literals to decide when to blacklist low scaling factors

chrome/browser/ui/libgtk2ui/gtk2_ui.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/browser/ui/libgtk2ui/gtk2_ui.h"
 
 #include <math.h>
 #include <pango/pango.h>
 #include <set>
 #include <utility>
@@ skipping 1337 matching lines @@
 }
 
 float Gtk2UI::GetDeviceScaleFactor() const {
   if (gfx::Display::HasForceDeviceScaleFactor())
     return gfx::Display::GetForcedDeviceScaleFactor();
   const int kCSSDefaultDPI = 96;
   const float scale = GetDPI() / kCSSDefaultDPI;
   // Round to 1 decimal, e.g. to 1.4.
   const float rounded = roundf(scale * 10) / 10;
   // See crbug.com/484400
-  return rounded < 1.3 ? 1.0 : rounded;
+  return rounded < 1.3f ? 1.0f : rounded;

[oshima, 2016/01/13 23:39:44]

I think it's better to be

return scale < 1.3f ? 1.0f : roundf(scale * 10) / 10;

[mario.endlessm, 2016/01/14 10:43:02]

Agreed. I just did not change it now because that changes the semantics a bit,
although they seem to change them for the better (or at least to be consistent
with the description of the initial patch), so I'll update the patch.

Thanks 

 }
 
 }  // namespace libgtk2ui
 
 views::LinuxUI* BuildGtk2UI() {
   return new libgtk2ui::Gtk2UI;
 }