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

Fallback for multiple sources does not work #6831

Closed
dchaur opened this issue Sep 3, 2020 · 2 comments
Closed

Fallback for multiple sources does not work #6831

dchaur opened this issue Sep 3, 2020 · 2 comments

Comments

@dchaur
Copy link

dchaur commented Sep 3, 2020

Description

It is a shame that since 2014 the fallback keeps failing using multiple sources.

Steps to reproduce

Open whatever editor an include video js.

  1. Include more than one source
  2. "Break" the first source just modifying the url making it invalid
  3. Run the player

Results

Expected

VideoJS follows the same approach as the standard HTML video, spec of "The resource selection algorithm for a media element" described on (https://html.spec.whatwg.org/multipage/media.html#concept-media-load-algorithm).

Actual

VideoJS does not fallback correctly trying to play the other available source.

Error output

VIDEOJS: ERROR: (CODE:4 MEDIA_ERR_SRC_NOT_SUPPORTED) The media could not be loaded, either because the server or network failed or because the format is not supported.

Additional Information

image

versions

videojs

All of them

browsers

All of them

OSes

All of them

plugins

no.

@welcome
Copy link

welcome bot commented Sep 3, 2020

👋 Thanks for opening your first issue here! 👋

If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
To help make it easier for us to investigate your issue, please follow the contributing guidelines.

@gkatsev
Copy link
Member

gkatsev commented Sep 4, 2020

This is basically expected behavior right now, and we have a long-standing issue to fix it #1805.
We hope to finally fix it in the next quarter.

@gkatsev gkatsev closed this as completed Sep 4, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants