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

fix(FEC-7836): seek doesn't work correctly on MAC safari on fullscreen #218

Merged
merged 3 commits into from
Apr 12, 2018

Conversation

odedhutzler
Copy link
Contributor

@odedhutzler odedhutzler commented Apr 11, 2018

Description of the Changes

Safari fullscreen element has >0 offset. Chrome (for example) gives it offset 0.

I added isfullscreen() check and set the offset to 0.

tested on mac(chrome+safari), ipad, xiomi & samsung tab 3

CheckLists

  • changes have been done against master branch, and PR does not conflict
  • new unit / functional tests have been added (whenever applicable)
  • test are passing in local environment
  • Travis tests are passing (or test results are not worse than on master branch :))
  • Docs have been updated

@odedhutzler odedhutzler self-assigned this Apr 11, 2018
@@ -270,6 +270,9 @@ class SeekBarControl extends Component {
_y += element.offsetTop - element.scrollTop;
element = element.offsetParent;
}
if (this.props.player.isFullscreen()) {
_x = 0;
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this is worth an inline comment, like

offset 0 is forced to handle browser compatibility issue

Copy link
Contributor Author

Choose a reason for hiding this comment

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

you are right

@odedhutzler odedhutzler merged commit 659df58 into master Apr 12, 2018
@odedhutzler odedhutzler deleted the FEC-7836 branch April 12, 2018 06:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants