-
-
Notifications
You must be signed in to change notification settings - Fork 740
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
Comments
It usually happens whenever there is an update to frontend, eg new commit was pushed to master branch and CD published a new version. |
Is there a way to stop it from happening? Because it can get annoying when it happens in the middle of watching a video |
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. |
Enable "Store Watch History" to resume your progress in the video after the forced refresh after an update.
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. |
Duplicate of #1199 apparently |
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?
The text was updated successfully, but these errors were encountered: