[GH-ISSUE #491] getCurrentTime() On Plyr #347

Closed
opened 2026-02-26 02:32:55 +03:00 by kerem · 2 comments
Owner

Originally created by @Fahad-pnw on GitHub (Nov 30, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/491

Hi, can anyone please help me through putting a getCurrentTime() from Plyr next to the progressbar? i tried a few fails and failed to do it.

  • You have read and followed closely the Wiki, Upgrade Guide, as well as Troubleshooting
  • The issue has not been reported before
  • This is not a "how to install on Windows" or "why is my npm messed up" question
  • You're a cool person

All checked? Now also make sure your issue

  • Is associated with a version. Or better yet, a commit.
  • Is as detailed as possible (ahem... OS, browser, steps to reproduce, maybe?)
  • Includes the error output if it's a bug/error report ("Whoops!" is not very helpful, you know)
  • Is in English, 因为我不说中文。
Originally created by @Fahad-pnw on GitHub (Nov 30, 2016). Original GitHub issue: https://github.com/koel/koel/issues/491 Hi, can anyone please help me through putting a getCurrentTime() from Plyr next to the progressbar? i tried a few fails and failed to do it. - [x] You have read and followed closely the [Wiki](https://github.com/phanan/koel/wiki), [Upgrade Guide](https://github.com/phanan/koel/releases), as well as [Troubleshooting](https://github.com/phanan/koel/wiki/Troubleshooting) - [x] The issue has not been reported before - [x] This is not a "how to install on Windows" or "why is my npm messed up" question - [x] You're a cool person All checked? Now also make sure your issue - [x] Is associated with a version. Or better yet, a commit. - [x] Is as detailed as possible (ahem... OS, browser, steps to reproduce, maybe?) - [x] Includes the error output if it's a bug/error report ("Whoops!" is not very helpful, you know) - [x] Is in English, 因为我不说中文。
kerem closed this issue 2026-02-26 02:32:55 +03:00
Author
Owner

@phanan commented on GitHub (Dec 1, 2016):

How is this related to Koel?

<!-- gh-comment-id:264141866 --> @phanan commented on GitHub (Dec 1, 2016): How is this related to Koel?
Author
Owner

@Fahad-pnw commented on GitHub (Dec 2, 2016):

Its not an issue in koel but i didn't know better place to ask you or other devs working on this.
Now, you developed koel, so you integrated the plyr within it, i was thinking if i could display track time which is getCurrentTime() in plyr documentation, it would be awesome. can you please guide just an overview of a 2 liner or so, if you're busy that how i would go upon implementing that or simply display track played-duration which comes as a standard 00:00 sort of a way...

if you could please guide, i'd be much obliged.

<!-- gh-comment-id:264341668 --> @Fahad-pnw commented on GitHub (Dec 2, 2016): Its not an issue in koel but i didn't know better place to ask you or other devs working on this. Now, you developed koel, so you integrated the plyr within it, i was thinking if i could display track time which is getCurrentTime() in plyr documentation, it would be awesome. can you please guide just an overview of a 2 liner or so, if you're busy that how i would go upon implementing that or simply display track played-duration which comes as a standard 00:00 sort of a way... if you could please guide, i'd be much obliged.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#347
No description provided.