bc0cf6e4c7
Automatic update from web-platform-testsMake BlueTooth/USB requestDevice non-consuming.
The specs for both WebBlueTooth & WebUSB only require a user
activation during a requestDevice call. So consuming the activation
(vs just checking) is not a strong requirement. There was a concern
that "not consuming" could possibly mean multiple choosers for a single
user activation but our browser code already handles the situation
gracefully. Multiple requests to browser is possible from different
tabs anyway, even with (isolated) consumptions in individual tabs.
Therefore it makes sense to remove the consumption behavior here,
which is not spec-ed anyway. This would fit our goal of a simple
user activation model ("UserActivationV2" project) which should be
simple enough for cross-browser implementation and for a complete spec.
Bug: 786407
Change-Id: I3c9dbf43df34d4cb4a2a33214a6c44847fa7435b
Reviewed-on: https://chromium-review.googlesource.com/775866
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548768}
wpt-commits: 6ba01ea2ffbafbb329352628b244815654b38156
wpt-pr: 10130
wpt-commits: 6ba01ea2ffbafbb329352628b244815654b38156
wpt-pr: 10130
|
||
|---|---|---|
| .. | ||
| characteristic | ||
| descriptor | ||
| device/gattserverdisconnected-event | ||
| idl | ||
| requestDevice | ||
| resources | ||
| script-tests | ||
| server | ||
| service | ||
| generate_test.py | ||
| generate.py | ||
| OWNERS | ||
| README.md | ||
Web Bluetooth Testing
Web Bluetooth testing relies on the Web Bluetooth Testing API which must be provided by browsers under test.
In this test suite resources/bluetooth-helpers.js detects and triggers
the API to be loaded as needed.
The Chromium implementation is provided by
../resources/chromium/web-bluetooth-test.js.
The Chromium implementation is not included in stable Chrome builds since it
would add too much to the binary size. On Chromium infrastructure, it is run
using the content_shell executable.
In the future, Chromium src/device/bluetooth may be refactored into a Mojo
service. At this point, it would be possible to add the necessary testing hooks
into stable Chrome without substantially increasing the binary size, similar to
WebUSB.
These bluetooth tests are upstreamed here because other browsers can reuse them by implementing the Web Bluetooth Testing API, even if only on their internal infrastructure.
Generated gen-* files from generator.py
generator.py builds gen-*.html tests using templates in
script-tests/*/*.js.
The subdirectory structure in bluetooth/script-test/* is recreated into
bluetooth/*. The generator expands each CALL function from templates
into new leaf directories and files.
Example:
script-tests/server/get-same-object.js contains:
gattServer.CALLS([
getPrimaryService('heart_rate')|
getPrimaryServices()|
getPrimaryServices('heart_rate')[UUID]]),
Generating:
server/getPrimaryService/gen-get-same-object.html
server/getPrimaryServices/gen-get-same-object.html
server/getPrimaryServices/gen-get-same-object-with-uuid.html
Usage:
$ python generate.py
More details documented in generate.py.