Skip to content

Clear watch progress from view cache when removing video form history#2220

Merged
PrestonN merged 1 commit intodevelopmentfrom
fix/watch-progress-in-list-video-view
Apr 27, 2022
Merged

Clear watch progress from view cache when removing video form history#2220
PrestonN merged 1 commit intodevelopmentfrom
fix/watch-progress-in-list-video-view

Conversation

@Svallinn
Copy link
Member

@Svallinn Svallinn commented Apr 25, 2022

Pull Request Type

  • Bugfix
  • Feature Implementation

Description
On the channel view (and pretty much anywhere with a ft-list-video component), after removing a seen video from history through the context menu, the page would still remember the watch progress and delegate it to the external player afterwards, which was very annoying since most of those videos' previous watch progress is basically at the end of the video.
This PR clears that view's cached watch progress value after removing the video from history.

Additional notes
I personally don't care, but I'll leave it here as a note in case someone wants to look into it.
I noticed that the watch progress bar value doesn't always seem to be accurate.
It's possible that the calculation for this value is badly done or the values provided to the calculation itself are a bit off, I don't know ¯\_(ツ)_/¯

@cloudrac3r cloudrac3r removed their request for review April 25, 2022 07:44
@efb4f5ff-1298-471a-8973-3d47447115dc efb4f5ff-1298-471a-8973-3d47447115dc added the PR: waiting for review For PRs that are complete, tested, and ready for review label Apr 25, 2022
@PrestonN PrestonN merged commit 39bf592 into development Apr 27, 2022
@github-actions github-actions bot removed the PR: waiting for review For PRs that are complete, tested, and ready for review label Apr 27, 2022
@Svallinn Svallinn deleted the fix/watch-progress-in-list-video-view branch April 27, 2022 19:24
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.

5 participants