Handle floating point coordinates from ozone to exosphere

ui/events/event_utils.h

Index: ui/events/event_utils.h
diff --git a/ui/events/event_utils.h b/ui/events/event_utils.h
index c7a51aab0abb3ffe0dd50e08512f524e41dbac28..f1109a8950454901857451567010668161095076 100644
--- a/ui/events/event_utils.h
+++ b/ui/events/event_utils.h
@@ -70,6 +70,8 @@ EVENTS_EXPORT void ValidateEventTimeClock(base::TimeTicks* timestamp);
 // TODO(tdresser): Return gfx::PointF here. See crbug.com/337827.

[oshima, 2017/01/23 16:34:32]

We should be able to remove old one (we may want to do it in separate CL if this
has to be merged). Can you add this one to BUG too?

[sky, 2017/01/23 17:04:06]

If the only caller is from the constructor that was just changed, it should be
easy to remove it now.

 EVENTS_EXPORT gfx::Point EventLocationFromNative(

[sky, 2017/01/23 16:08:00]

Do we still call the non-floating point version?

[denniskempin, 2017/01/23 20:36:41]

The method is called in a couple of locations besides that Constructor and
unittests. See:
https://cs.chromium.org/search/?q=EventLocationFromNative&sq=package:chromium...

They are not many, but since we need to merge this into M56 (now stable or about
to be stable) I would like to keep the impact as low as possible. What do you
think?

     const base::NativeEvent& native_event);
+EVENTS_EXPORT gfx::PointF EventLocationFromNativeF(
+    const base::NativeEvent& native_event);
 
 // Gets the location in native system coordinate space.
 EVENTS_EXPORT gfx::Point EventSystemLocationFromNative(