Restarting your apps while the network is offline makes you realize some things are silly… like needing to click the Reload button in #web#browsers' error pages, when they very well know when the operating system is fully back online anyway.
Therefore, I filed a request for #GNOMEWeb / #Epiphany to do that for me when #GNOME / #NetworkManager signals that online connectivity has been restored: https://gitlab.gnome.org/GNOME/epiphany/-/issues/2230
@cassidy I couldn't be bothered to come up with a better error message (also I don't know if that's done by WebKitGTK instead of Epiphany), so thank you for commenting there and reading my lazy mind 😏️
@topher@nekohayo I hate to say “another preference” but I imagine it could make sense here. Though I do wonder if the concern is security/exposing requests, if it should be Network Manager defending against network changes rather than up to the browser. Because other apps don’t ask before touching the network after a change…
At the very least, maybe even a contextual option:
Suppose, for one, that I am connecting to a metered network with limited data. Conveniently, all my browser windows and tabs are at offline error pages, so upon connecting, there should be very limited traffic. Yet, upon connecting, there's now 100MB of every browser tab I assumed would remain in its errored state suddenly surprise refreshing itself
In addition of course to the VPN, DNS, compartmentalised separate network concerns others beat me to
@cassidy@topher Yup, that's why from the get go I mentioned exceptions for metered, captive & LAN in the ticket's 3rd paragraph, and tagged it "Initiative: Metered data". Basically only do the auto-retry when the runway is clear. In my view, NetworkManager would withhold any auto-loading when on inconsistent or limited networks, and beyond that Epiphany will refuse to connect to invalid HTTPS anyway, so seems safe to me.
@bp What form? Talking about the case where the user is sitting in front of a "Could not load this page" error page already (screenshot in the ticket)…
@nekohayo I really like this idea in theory, but I wonder could it end up inadvertently exposing DNS and other network requests to a potentially-hostile network for a VPN user when a change of underlying network becomes necessary?
Add comment