Skip to content

All the tabs with Piped open refresh automatically #1906

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

Closed
1 task
mojo-jojo-7 opened this issue Dec 21, 2022 · 5 comments
Closed
1 task

All the tabs with Piped open refresh automatically #1906

mojo-jojo-7 opened this issue Dec 21, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@mojo-jojo-7
Copy link

Official Instance

Describe the bug

All the tabs with Piped open refresh randomly by themselves. I tried to understand when this happens, but could not find any pattern. It even happens while watching a video.

To Reproduce

Not sure how to reproduce this when wanted. I guess you just have to catch it when it happens

Expected behavior

No automatic refreshes

Logs/Errors

None

Browser, and OS with Version.

Firefox 108.0.x on Windows 10

Additional context

I'm using https://piped.kavin.rocks and it happens almost everyday. I did not observe this behavior on the official instance, but it's possible I did not use it enough to catch it happening. Perhaps it's some kind of push from the server due to an update?

@mojo-jojo-7 mojo-jojo-7 added the bug Something isn't working label Dec 21, 2022
@goodness-from-me
Copy link

It usually happens whenever there is an update to frontend, eg new commit was pushed to master branch and CD published a new version.

@mojo-jojo-7
Copy link
Author

Is there a way to stop it from happening? Because it can get annoying when it happens in the middle of watching a video

@Bnyro
Copy link
Member

Bnyro commented Dec 21, 2022

I somewhat doubt that's the reason, the frontend only consists of static files that are downloaded from the server once and then run on your browser. When there's an update/new commit to the frontend there's nothing that tells the browser to refresh the page as those files are only statically served.

@AlyoshaVasilieva
Copy link
Contributor

Enable "Store Watch History" to resume your progress in the video after the forced refresh after an update.

When there's an update/new commit to the frontend there's nothing that tells the browser to refresh the page as those files are only statically served.

If you go to an instance after a few days of not using it, it doesn't load then refresh the page after a few seconds for you? This is reproducible for me on every instance. Also, if I manually update my private instance (build, pull, down, up), including frontend, and I visit it it will always force a refresh for me.

@Bnyro
Copy link
Member

Bnyro commented Jan 26, 2023

Duplicate of #1199 apparently

@Bnyro Bnyro closed this as not planned Won't fix, can't repro, duplicate, stale Jan 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants