docs: add note for Safari captions error #174
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gesinger
reviewed
Jul 30, 2018
docs/troubleshooting.md
Outdated
| @@ -37,3 +38,10 @@ you need to properly configure CORS on your server: https://github.com/videojs/h | |||
| Some browsers support native playback of certain streaming formats. By default, we defer to the native players. However, this means that features specific to videojs-http-streaming will not be available. | |||
|
|
|||
| Solution: use videojs-http-streaming based playback on those devices: https://github.com/videojs/http-streaming#overridenative | |||
|
|
|||
| ## media_err_decode error on Desktop Safari | |||
There was a problem hiding this comment.
Probably worth using all caps since the error comes back in all caps
docs/troubleshooting.md
Outdated
|
|
||
| ## media_err_decode error on Desktop Safari | ||
|
|
||
| This error may occur if the source manifest has `CLOSED-CAPTIONS=NONE` and an external text track is loaded into the player. Safari does not allow the inclusion any captions if the manifest indicates that captions will not be provided. |
There was a problem hiding this comment.
We may also want to mention that MEDIA_ERR_DECODE can happen for a number of reasons, as it is particularly common for misconfigured content, the captions being just one of them.
gesinger
reviewed
Jul 30, 2018
docs/troubleshooting.md
Outdated
| @@ -9,6 +9,7 @@ For issues around data embedded into media segments (e.g., 608 captions), see th | |||
| - ["No compatible source was found" on IE11 Win 7](#no-compatible-source-was-found-on-ie11-win-7) | |||
| - [CORS: No Access-Control-Allow-Origin header](#cors-no-access-control-allow-origin-header) | |||
| - [Desktop Safari/iOS Safari/Android Chrome/Edge exhibit different behavior from other browsers](#desktop-safariios-safariandroid-chromeedge-exhibit-different-behavior-from-other-browsers) | |||
| - [media_err_decode error on Desktop Safari](#media_err_decode-error-on-desktop-safari) | |||
There was a problem hiding this comment.
One more spot for all caps
gesinger
approved these changes
Jul 30, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update documentation to handle a Safari decode error scenario