Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail playback after long waitingforkey #484

Open
xhwang-chromium opened this issue May 7, 2021 · 2 comments
Open

Fail playback after long waitingforkey #484

xhwang-chromium opened this issue May 7, 2021 · 2 comments
Milestone

Comments

@xhwang-chromium
Copy link
Contributor

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.

@joeyparrish
Copy link
Member

I think it could be difficult to define a fixed interval for that. But in general, if an application isn't addressing this event, it's reasonable to fail playback at some point.

@joeyparrish
Copy link
Member

Moving to v3 to give the community time to comment. If there's any desire for this, let us know. For now, we're kicking this out of the v2 milestone.

@joeyparrish joeyparrish added this to the V3 milestone Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants