Revision 6ba01ea2ffbafbb329352628b244815654b38156 authored by Mustaq Ahmed on 06 April 2018, 14:14:32 UTC, committed by Blink WPT Bot on 06 April 2018, 14:33:48 UTC
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}
1 parent 0cddb68
File | Mode | Size |
---|---|---|
resources | ||
OWNERS | -rw-r--r-- | 25 bytes |
content-security-policy.https.window.js | -rw-r--r-- | 768 bytes |
credentials-in-url.https.window.js | -rw-r--r-- | 1.2 KB |
dangling-markup.https.window.js | -rw-r--r-- | 709 bytes |
interfaces-worker.https.html | -rw-r--r-- | 509 bytes |
interfaces.html | -rw-r--r-- | 1.1 KB |
interfaces.worker.js | -rw-r--r-- | 835 bytes |
mixed-content-and-allowed-schemes.https.window.js | -rw-r--r-- | 3.2 KB |
port-blocking.https.window.js | -rw-r--r-- | 1.3 KB |
Computing file changes ...