- From: Jim Evans <james.h.evans.jr@gmail.com>
- Date: Mon, 9 Jan 2017 11:34:57 -0500
- To: public-browser-tools-testing <public-browser-tools-testing@w3.org>
On Jan 9, 2017, at 06:19, Simon Stewart <simon.m.stewart@gmail.com> wrote: > After discussing this on the IRC channel with James, I'd like to make a proposal for modifying pointerMove, but it'd be handy to have a discussion here before I make edits to the spec. > > Proposal: > > Add an "origin" property to the pointerMove command. This could be one of three values "absolute", "input state" or an element reference, and would default to "absolute" if not specified. The x/y offsets are assumed to be relative to the origin. In the main, I'm pretty happy with this as a proposal. Yes, this is a case I think we overlooked in Redmond, and the proposed solution allows for the ability to implement the existing Selenium API, as well as being relatively non-disruptive to what we had before. Even this late in the game, we do need the functionality available for a number of user scenarios. +1 from me. Jim
Received on Monday, 9 January 2017 16:35:58 UTC