-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Add crossorigin documentation and explanation and update examples #1888
Comments
More info: This is because native text tracks with VTT files on other origins require crossorigin="anonymous" on the video element to work but in some browsers if the crossorigin attribute is set but the video (mp4 in chrome, for example) doesn't have CORS headers set up as well then the video will fail. |
👍 I get the following error in Chrome Version 44.0.2403.157 (64-bit). No differences with crossorigin="anonymous". Problem is known CORS issue, but error unclear. Is the errorHandler not forwarding the exact error message?
|
At least on iOS, we cannot use native text tracks with cross-domain tracks without applying the
crossorigin="anonymous"
property to the video element. We should apply that where appropriate.Different browser react differently to that attribute, so, we definitely don't want to apply it by default. We want to apply it to a targeted range of browsers.
The takeaway from #2269:
The text was updated successfully, but these errors were encountered: