W3C home > Mailing lists > Public > public-device-apis-log@w3.org > September 2018

Re: [sensors] Introduce WebDriver extension API

From: Wanming Lin via GitHub <sysbot+gh@w3.org>
Date: Wed, 12 Sep 2018 07:02:25 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-420535500-1536735743-sysbot+gh@w3.org>
For 3, you may misunderstand the WPT's testdriver.js, it is actually based on WebDriver. 
You can find some hints in the first [PR ](https://github.com/web-platform-tests/wpt/pull/6897/files) that implement click automation or in the @kereliuk's [slides ](https://docs.google.com/presentation/d/1mNkQ94mArD1xqfPNxYijOzb28SsOm9Gi0IQl3A35BSs/edit#slide=id.p)that introduce the testdriver.js. 

e.g. for `test_driver.click(element)`, the basic flow is the click call would result in a request containing selector that could be used to locate the element, allowing the [server ](https://github.com/web-platform-tests/wpt/blob/master/tools/wptrunner/wptrunner/executors/executorselenium.py#L129)to send a `Find Element(selector)` call followed by a `Click(element)` call. It would then return a response, causing the promise to resolve.

So, we should just base on the 2 to wrap this extension API into testdriver.js for WPT.

 > I'd also seen the WebDriver bits in the Permissions and Reporting specs, but I couldn't see them actually being used anywhere for comparison.

Seems they're not yet implemented in any driver of vendors.

GitHub Notification of comment by Honry
Please view or discuss this issue at https://github.com/w3c/sensors/pull/369#issuecomment-420535500 using your GitHub account
Received on Wednesday, 12 September 2018 07:02:31 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:55 UTC