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(subtitles): Consider hidden tracks as active #564

Merged
merged 2 commits into from
Dec 6, 2019

Conversation

mister-ben
Copy link
Contributor

Description

cuechange events should be triggered for a track with mode hidden. Currently a track is only considered active if its mode is showing, cues will not be parsed and no cuechange occurs.

Specific Changes proposed

Check for hidden as well as showing.

Requirements Checklist

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

misteroneill
misteroneill previously approved these changes Jun 25, 2019
@gkatsev
Copy link
Member

gkatsev commented Jun 25, 2019

Hm... I seem to be able to listen to the cuechange even of the 608 track in bipbop with and without this change...

@gkatsev
Copy link
Member

gkatsev commented Jun 25, 2019

At least in master, currently.

@mister-ben
Copy link
Contributor Author

That has a default track which starts as showing. When you change its mode to hidden the cues from the vtt segments which were already parsed still exist on the track and will trigger cuechange. Once you get beyond the end of that range no new cues will be added.

@gkatsev
Copy link
Member

gkatsev commented Jun 26, 2019

The 608 track isn't on by default and that's the one I listened to cuechange on.

@mister-ben
Copy link
Contributor Author

Ah, 608. This fixes the vtt segments. With this, they'll behave like the 608 or a remote text track would.

@stale
Copy link

stale bot commented Aug 25, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the outdated label Aug 25, 2019
@mister-ben
Copy link
Contributor Author

Shouldn't go stale

@stale stale bot removed the outdated label Aug 26, 2019
Copy link
Member

@gkatsev gkatsev left a comment

Choose a reason for hiding this comment

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

I'm just going to accept this. The change makes sense, even if I haven't been able to quite verify it.

@stale
Copy link

stale bot commented Oct 25, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the outdated label Oct 25, 2019
@stale stale bot closed this Nov 1, 2019
@mister-ben mister-ben reopened this Nov 4, 2019
@stale stale bot removed the outdated label Nov 4, 2019
@gkatsev gkatsev merged commit d510a1e into videojs:master Dec 6, 2019
gkatsev pushed a commit that referenced this pull request Dec 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants