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

docs: update troubleshooting guide for Edge/mobile Chrome #216

Merged
merged 2 commits into from Sep 6, 2018

Conversation

forbesjo
Copy link
Contributor

Description

Update troubleshooting guide for Edge/mobile Chrome (see #211)

Requirements Checklist

  • Feature implemented / Bug fixed
  • If necessary, more likely in a feature request than a bug fix
  • Reviewed by Two Core Contributors

@forbesjo forbesjo added the chore label Aug 29, 2018
@@ -35,7 +35,9 @@ you need to properly configure CORS on your server: https://github.com/videojs/h

## Desktop Safari/iOS Safari/Android Chrome/Edge exhibit different behavior from other browsers

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.
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extra space

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.
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.

On Edge and mobile Chrome 608 captions, ID3 tags or live streaming may not work as expected with native playback, it is recommended that `overridenative` be used on those platforms if necessary.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe a , after Chrome. Two spaces before overridenative. overridenative => overrideNative

@forbesjo forbesjo merged commit 21e5335 into master Sep 6, 2018
@forbesjo forbesjo deleted the forbesjo-patch-1 branch September 6, 2018 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants