You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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 thewaitingforkey
event, user will get a clearer signal on the issue.The text was updated successfully, but these errors were encountered: