W3C home > Mailing lists > Public > public-test-infra@w3.org > April to June 2017

Re: Specifications with matching test APIs

From: James Graham <james@hoppipolla.co.uk>
Date: Mon, 24 Apr 2017 15:32:28 +0100
To: public-test-infra@w3.org
Message-ID: <73a3f716-8f64-7bd4-7216-bf329a6b1e12@hoppipolla.co.uk>
On 22/04/17 02:28, Reilly Grant wrote:
> On Fri, Apr 21, 2017 at 6:11 PM Rick Byers <rbyers@chromium.org> wrote:
>> Thanks Reilly, I support continuing to move in this direction!
>> Are you planning in shipping this API in release Chrome builds behind a
>> flag?  I think it would be reasonable to modify the WPT infrastructure
>> (stability_checker, dashboard) to pass a --enable-testing-apis flag
>> (although we might need to consider the security implications of that for
>> the WPT infrastructure running potentially untrusted test patches).  But I
>> don't think we'd want to use content_shell (or even Chromium builds) in
>> that infrastructure - at least not in place of Chrome builds.
> The ability to override the Mojo services provided to the renderer from the
> renderer itself (which is how Chromium's polyfill for this API is
> implemented) is only available in content_shell when the --run-layout-test
> parameter is passed. There have been discussions with the Mojo team about
> making this available in production Chrome builds when a flag is enabled.
> It would have to be a flag which displays the "unsupported flag, security
> and stability will suffer" infobar because it effectively allows arbitrary
> JavaScript to run with the privileges of the renderer.

This seems like:

* An API with unclear vendor buy-in.
* An test API that is (effectively) not available outside Chromium CI 
(although it's possible to get contentshell builds it's not a bad 
approximation to assume that no one will).

So I'm pretty worried about this approach. It seems like there's a high 
chance that the test api will encode Blink implementation details, we 
will struggle to run the tests outside your CI, and web developers who 
want to test their USB-using website will be left to search for a 
different solution.
Received on Monday, 24 April 2017 14:32:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:34:13 UTC