- From: Xiaohan Wang via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 May 2021 19:46:00 +0000
- To: public-html-media@w3.org
xhwang-chromium has just created a new issue for https://github.com/w3c/encrypted-media: == Fail playback after long waitingforkey == According to the current spec, when playback is blocked waiting for a key, a `waitingforkey` event will be fired on the media element. However, from my experience, a lot of JS players don't handle this event. Since there are not error on the media element, the playback will simply stall. This often leads to bad user experiences: users will only see hanging pages without clear signal on what's happening. I propose that we change the spec such that after `waitingforkey` for long enough (e.g. 30 seconds), if the playback doesn't resume, we trigger an error on the media element, so even if the JS player doesn't handle the `waitingforkey` event, user will get a clearer signal on the issue. Please view or discuss this issue at https://github.com/w3c/encrypted-media/issues/484 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 7 May 2021 19:46:03 UTC