- From: Wanming Lin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Oct 2017 06:13:18 +0000
- To: public-device-apis-log@w3.org
@marcoscaceres, @andrey-logvinov, I address tasks that I think we can do in Wake Lock test suites below. Could you please review it and supplement if I miss something else? - [ ] Web IDL tests - [ ] Convert [Chromium Layout tests](https://chromium.googlesource.com/chromium/src.git/+/master/third_party/WebKit/LayoutTests/wake_lock/) to w-p-t - [ ] Feature policy - [ ] Wake Lock must not be exposed in an insecure context - [ ] Pass valid/invalid `WakeLockType` to `getWakeLock` - [ ] Monitor `activechange` event to check current wake lock status indicated by the active attribute - [ ] No exception is thrown when invoking `cancel()` twice - [ ] Fail to acquire the wake lock when a Document is failed to [request the wake lock](https://w3c.github.io/wake-lock/#dfn-requesting-the-wake-lock) - [ ] The screen wake lock MUST NOT be applicable after the screen is manually swiched off by the user until it is switched on again. (Manual) - [ ] TBD -- GitHub Notification of comment by Honry Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/111#issuecomment-339562159 using your GitHub account
Received on Thursday, 26 October 2017 06:13:22 UTC