- From: James Graham <james@hoppipolla.co.uk>
- Date: Tue, 4 Apr 2017 10:21:17 +0100
- To: public-test-infra@w3.org
On 04/04/17 04:40, Vincent Scheib wrote: > Even a Web Driver extension would require browsers to expose an API, and > that costs code size for a testing only feature. The reasons for preferring a WebDriver API where appropriate are twofold. Principally exposing things through WebDriver allows web developers to use them to test sites; an important part of the story around making the web a more appealing platform. The secondary reason is that integrating with an existing spec makes it obvious what quality bar has to be met for these testing features, which helps alleviate the concern around ending up with tests that are nominally cross-vendor but actually tied to a specific implentation.
Received on Tuesday, 4 April 2017 09:21:47 UTC