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

Standalone Player: 60th sec (2:60) is displayed in the player #1975

Closed
Karthikeya212 opened this issue May 31, 2017 · 6 comments

Comments

Projects
None yet
5 participants
@Karthikeya212
Copy link
Collaborator

commented May 31, 2017

Server: https://avalonmediasystem.github.io/avalon-poc-standalone/dist/
Testing: Smoke
Browser: Chrome(58.0.3029.110 (64-bit))
Flash version: 24.0.0.221
Operating System: Windows10
Issue: 60th sec (2:60) is displayed in the player.

Expected behavior

60th sec should be represented as 00 (after 2:59 next second should be 3:00 and not 2:60, the player is showing both 2:60 and 3:00)

Actual behavior

The player is showing both 2:60 and 3:00

Steps to reproduce the behavior

  1. Open the above mentioned server location.
  2. Go to the Audio(Video) player and start playing.
  3. Observe at the end of every minute the timeline displays the 60th sec as well as the 00th sec.
    60th sec_1
    60th sec_2

Related work

Link to related tickets or prior related work here.

@davidschober

This comment has been minimized.

Copy link

commented May 31, 2017

This seems like an upstream issue. We didn't mess around with the player's math correct? @adamjarling can you investigate briefly and kick off an upstream bug/pr

@adamjarling

This comment has been minimized.

Copy link
Contributor

commented May 31, 2017

Sure, I can look into. As of now we don't manually manipulate the clock or display. Although we do adjust the current time when clicking on sections.

@joncameron joncameron modified the milestone: Backlog Jun 23, 2017

@adamjarling adamjarling self-assigned this Jul 13, 2017

@adamjarling

This comment has been minimized.

Copy link
Contributor

commented Jul 13, 2017

How about we time box this at a '2' for initial investigation?

@joncameron

This comment has been minimized.

Copy link
Contributor

commented May 16, 2019

Closing this bug as stale. It hasn't been reported for a very long time.

@joncameron joncameron closed this May 16, 2019

@cjcolvar

This comment has been minimized.

Copy link
Member

commented May 23, 2019

@joncameron I definitely still see this for certain items. It came up as recently as during 6.5 regression testing.

@davidschober

This comment has been minimized.

Copy link

commented May 23, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.