Enable floating point touch co-ordinates in EventSender

Enable floating point touch co-ordinates in EventSender

WebTouchPoint has used floating point co-ordinate and radius values for awhile, but we've never allowed generating non-integer values via EventSender.

BUG=323935
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=275340

[Rick Byers, 2014-06-05 21:28:08]

Dirk, can you please review this little EventSender fix?  It's a prerequisite
for my blink changes here: https://codereview.chromium.org/298133003/

[Dirk Pranke, 2014-06-05 21:35:28]

seems fine on its own, but I'm not sure I understand how you'll land this and
the other change; wouldn't this need to be some sort of 3-sided patch?

[Rick Byers, 2014-06-05 21:48:23]

On 2014/06/05 21:35:28, Dirk Pranke wrote:
> seems fine on its own, but I'm not sure I understand how you'll land this and
> the other change; wouldn't this need to be some sort of 3-sided patch?

No, I don't think so.  WebTouchPoint has had it's members as float for awhile,
so that's already done (was needed because bits of content use WebTouchPoint
internally as the common event type between Android and Aura).  My blink change
just plumbs that down through the rest of blink.  But I can't test that without
landing this first.  The existing users of eventSender will continue to work as
a result of this change (no-one tries to pass a float AFAICT).

[Dirk Pranke, 2014-06-05 21:54:03]

On 2014/06/05 21:48:23, Rick Byers wrote:
> On 2014/06/05 21:35:28, Dirk Pranke wrote:
> > seems fine on its own, but I'm not sure I understand how you'll land this
and
> > the other change; wouldn't this need to be some sort of 3-sided patch?
> 
> No, I don't think so.  WebTouchPoint has had it's members as float for awhile,
> so that's already done (was needed because bits of content use WebTouchPoint
> internally as the common event type between Android and Aura).  My blink
change
> just plumbs that down through the rest of blink.  But I can't test that
without
> landing this first.  The existing users of eventSender will continue to work
as
> a result of this change (no-one tries to pass a float AFAICT).

okay, wasn't sure. lgtm.

[Rick Byers, 2014-06-05 22:03:40]

On 2014/06/05 21:54:03, Dirk Pranke wrote:
> On 2014/06/05 21:48:23, Rick Byers wrote:
> > On 2014/06/05 21:35:28, Dirk Pranke wrote:
> > > seems fine on its own, but I'm not sure I understand how you'll land this
> and
> > > the other change; wouldn't this need to be some sort of 3-sided patch?
> > 
> > No, I don't think so.  WebTouchPoint has had it's members as float for
awhile,
> > so that's already done (was needed because bits of content use WebTouchPoint
> > internally as the common event type between Android and Aura).  My blink
> change
> > just plumbs that down through the rest of blink.  But I can't test that
> without
> > landing this first.  The existing users of eventSender will continue to work
> as
> > a result of this change (no-one tries to pass a float AFAICT).
> 
> okay, wasn't sure. lgtm.

Thanks.  Clarified this in the CL description.

[Rick Byers, 2014-06-05 22:03:43]

The CQ bit was checked by rbyers@chromium.org

[commit-bot: I haz the power, 2014-06-05 22:08:04]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/rbyers@chromium.org/316303002/1

[commit-bot: I haz the power, 2014-06-06 05:25:10]

Change committed as 275340