Auto-reload when coming back online

Fri Oct 14 18:40:51 UTC 2016

I'd like to reinstate this.

As usual, if a web page returns in the headers that cache is not 
allowed, then the browser is supposed not to cache anything. This is 
only for information that has been allowed to cache according to the 
server reponse's headers.

If a user wants to overload the answer of a server, that's the job for 
an extension.

On 21-03-2016 01:22, Bram Pitoyo wrote:
> Like Matthew and Gijs wrote, if Necko can support this, then the 
> behaviour will have to be thought of very carefully.
>
> For instance, while it’s clear that site opened in PBM shouldn’t 
> auto-reload, it’s unclear whether normal mode should have the same 
> behaviour. On most sites, it’s okay. On mydatingsite.com 
> <http://mydatingsite.com>, it’s potentially embarrassing. Maybe this 
> would be a control that we should provide to users: Do you want sites 
> to auto-reload when you reconnect to the internet, or not?
>
>
> What Brunoais wrote is really interesting, too. It opens up the 
> possibility for Firefox to become a limited offline-browser that you 
> can use to go to the “last known good” version of any website, as long 
> as you’ve kept the cache. Two questions for consideration, though:
>
>  1. Have somebody thought of this idea before, and why didn’t any
>     modern browser do this? Is there enough value to devote
>     engineering resource?
>  2. How to serve a cached page and signal to the user that they cannot
>     interact with this page like an online page (no clicking on the
>     link, JS may not work well, etc.), and in fact, that their
>     internet is still offline?
>
>
> What do you think?
>
>
> On Sat, Mar 19, 2016 at 12:00 AM, Brunoais <brunoaiss at gmail.com 
> <mailto:brunoaiss at gmail.com>> wrote:
>
>     I think the idea was mentioned like this:
>     Firefox should be built aware enough such that if I order it to
>     reload a page and the version in cache is faulty (E.g. DNS fail),
>     the page should load directly form the internet instead of showing
>     what is in the cache.
>
>     I'd add more to it. I'd like a mechanism where a page in cache is
>     NOT deleted if either DNS or TCP fails allowing me to get the
>     earliest contents from a page after a failure to get the most
>     updated data.
>
>     If you are open for it, I'm open to propose a use-case on how to
>     get those kinds of results.
>
>
>     On 18-03-2016 10:20, Gijs Kruitbosch wrote:
>>     I'd also say there are "interesting" privacy aspects to this, and
>>     it might violate the principle of least surprise if we
>>     automatically reloaded the page. If I'm trying to load
>>     www.mydatingsite.com <http://www.mydatingsite.com> on my way to
>>     work, and the signal on the subway/tube is too rubbish to do so,
>>     I might not necessarily want it to be loaded automatically once I
>>     connect to the (employer-monitored) work wifi... Such a situation
>>     is likely to be the minority case, but we should keep it in mind
>>     when designing such a feature.
>>
>>     ~ Gijs
>>
>>     On 18/03/2016 05:07, Matthew N. wrote:
>>>     I think the main problem was that Necko (networking in Gecko)
>>>     didn't have good, if any, detection of network changes until
>>>     recently. There has been work on this in the last year but I
>>>     don't know the current state of it and it may vary by platform.
>>>     There is discussion on mozilla.dev.tech.network today about
>>>     network change detection and IPv6 so I think it's something
>>>     still on the radar.
>>>
>>>     CC'ing mozilla.dev.tech.network to see what the Necko team has
>>>     to say about whether we can support this in Firefox yet.
>>>
>>>     Matthew N. (:MattN)
>>>
>>>     On Thu, Mar 17, 2016 at 9:29 PM, Bram Pitoyo <bram at mozilla.com
>>>     <mailto:bram at mozilla.com>> wrote:
>>>
>>>         If a URL is loaded when there’s no internet connection,
>>>         Firefox will throw an error page, as expected.
>>>
>>>         But if my internet is back online, I still have to manually
>>>         reload this site. I would like to propose a slightly
>>>         different behaviour: pages that fail to load while the
>>>         browser is offline should reload automatically.
>>>
>>>         The result:
>>>
>>>           * I know that my internet is back on because Firefox now
>>>             shows the page I had failed to load
>>>           * I save a little bit of time by not needing to click
>>>             “Reload” or hit Ctrl+R
>>>
>>>         Have we thought of a behaviour like this?
>>>
>>>         _______________________________________________
>>>         firefox-dev mailing list
>>>         firefox-dev at mozilla.org <mailto:firefox-dev at mozilla.org>
>>>         https://mail.mozilla.org/listinfo/firefox-dev
>>>
>>>
>>>
>>>
>>>     _______________________________________________
>>>     firefox-dev mailing list
>>>     firefox-dev at mozilla.org <mailto:firefox-dev at mozilla.org>
>>>     https://mail.mozilla.org/listinfo/firefox-dev
>>
>>
>>
>>     _______________________________________________
>>     firefox-dev mailing list
>>     firefox-dev at mozilla.org <mailto:firefox-dev at mozilla.org>
>>     https://mail.mozilla.org/listinfo/firefox-dev
>
>
>     _______________________________________________
>     firefox-dev mailing list
>     firefox-dev at mozilla.org <mailto:firefox-dev at mozilla.org>
>     https://mail.mozilla.org/listinfo/firefox-dev
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/firefox-dev/attachments/20161014/3e833006/attachment.html>