- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Sep 2022 23:43:54 +0000
- To: public-device-apis-log@w3.org
> It looks like requiring transient activation [is not a normative requirement](https://html.spec.whatwg.org/multipage/media.html#allowed-to-play) for the <video> tag. I am not familiar with which browsers enforce this requirement. Sorry, I wasn't very clear. The transient activation aspect I was referring to was the act of pressing the play button. > One data point is that [NoSleep.js](https://github.com/richtr/NoSleep.js) recommends wrapping the call to their library in an input handler. I assume that is because it falls back to using a <video> element and some browsers require user activation to play a video (or to take a wake lock while playing video). Yes, exactly that. That's to allow the video to play with audio, even though it's silent (Safari detects it a video that's making noise). ![Screen Shot 2022-09-29 at 9 42 55 am](https://user-images.githubusercontent.com/870154/192907377-41aabd05-98ef-408a-941f-6bf3b75a8e57.png) -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/pull/351#issuecomment-1261576359 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 September 2022 23:43:56 UTC