Use float literals to decide when to blacklist low scaling factors

chrome/browser/ui/libgtk2ui/gtk2_ui.cc

Index: chrome/browser/ui/libgtk2ui/gtk2_ui.cc
diff --git a/chrome/browser/ui/libgtk2ui/gtk2_ui.cc b/chrome/browser/ui/libgtk2ui/gtk2_ui.cc
index f3e98fc104a82714fb25abd23b71aa573749654b..dc7485f87f1d31d9ce81f900b6999117b20e086a 100644
--- a/chrome/browser/ui/libgtk2ui/gtk2_ui.cc
+++ b/chrome/browser/ui/libgtk2ui/gtk2_ui.cc
@@ -1355,7 +1355,7 @@ float Gtk2UI::GetDeviceScaleFactor() const {
   // 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