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
Constantly seeing offline screen #1810
Comments
|
Thanks for flagging, we'll look into this. |
|
I'm experiencing the same problem with slightly different symptoms. Test system: Firefox 66.0.2 on Ubuntu 18.04.2 LTS To reproduce:
Simple reloading does nothing, however Ctrl + F5 resolves the issue. |
|
I've added additional logging to Service Worker. If anybody ever come across an aggressive offline page, please share the logging from your browser console. |
|
Hi! :) I went over to dev.to and opened the article How to Be Great? Just Be Good, Repeatably , clicked on the link in the first line, navigating to the authors blog. I have attached the console output starting from the time I first visited dev.to: console.log The relevant part of the log is probably this, right after I had hit browser back: |
|
Thanks for quick report @danielw93 . Are you using privacy badger or uMatrix by any chance? Is this reproducible in incognito? |
|
@maestromac Good call! |
|
Yeah, Service Worker is still a bit wonky and is false positive to extensions like Privacy Badger. Thanks for checking! Are you still experiencing this issue @stereobooster ? |
|
Hey @maestromac. No it was one time thing if we talk about offline screen issue. |
|
Alrighty, I'm assuming this issue is resolved. Please let me know if otherwise!! |
Describe the bug
Opened direct link to dev.to article and saw offline screen.
Cmd+Rdidn't help. I was online all the time. The only thing which is helped is to remove ServiceWorker completely and reload page.To Reproduce
Steps to reproduce the behavior:
Expected behavior
No offline screen if browser is online
Screenshots
N/A
Desktop (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: