- From: James Graham <james@hoppipolla.co.uk>
- Date: Wed, 04 Mar 2015 17:03:53 +0000
- To: Jason Leyba <jleyba@google.com>, "public-browser-tools-testing@w3.org" <public-browser-tools-testing@w3.org>
On 04/03/15 16:42, Jason Leyba wrote: > That use case can be solved in client libraries and shouldn't require > extra complexity at the spec/protocol level. I think that argument applies to almost every command though. All of navigation, all of findElement[s], adding cookies, most of element state, and lots of other parts of the protocol could be implemented purely in clients in terms of execute_script. AIUI there is no design goal to find the minimal possible protocol, but to find some useful compromise between minimalism and implementation complexity. AFAICT the current design that uses an opaque set of WebDriver-only window identifiers is not the right point on that complexity curve; it makes doing simple things hard and the benefits are unclear.
Received on Wednesday, 4 March 2015 17:04:18 UTC