- From: Andreas Tolfsen <ato@mozilla.com>
- Date: Fri, 10 Apr 2015 13:48:34 +0100
- To: public-browser-tools-testing <public-browser-tools-testing@w3.org>
On 10 Apr 2015, at 13:23, James Graham <james@hoppipolla.co.uk> wrote: > 1) It's an entirely backwards-compatible change so can be added at any > time in the future. … > 3) It's trivial to implement in clients in a way that covers all the use > cases for the current spec (i.e. interacting with web browsers). I think the concern is that if we don't define it, API local ends who do implement a shim for it could end up implementing it wrongly. My argument is that Selenium is free to mandate its behaviour and that it's in such a regard not a big problem if we don't have it in the spec. Additionally, it would regardless be consistent across browsers in a single language binding which isn't the case now. If Selenium really wants to be pedantic about this, it could ship a local end atom.
Received on Friday, 10 April 2015 12:49:06 UTC