<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>I'd like to reinstate this.</p>
<p>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.</p>
<p>If a user wants to overload the answer of a server, that's the
job for an extension.<br>
</p>
<br>
<div class="moz-cite-prefix">On 21-03-2016 01:22, Bram Pitoyo wrote:<br>
</div>
<blockquote
cite="mid:CAAicQ-15dUdCYjAYNtjYxdwpN1vnTWrKyAdtpZm5aS+7dFvpqA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>Like Matthew and Gijs wrote, if Necko can support
this, then the behaviour will have to be thought of very
carefully.<br>
<br>
</div>
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 <a moz-do-not-send="true"
href="http://mydatingsite.com" target="_blank">mydatingsite.com</a>,
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?<br>
</div>
<br>
<br>
</div>
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:<br>
<ol>
<li>Have somebody thought of this idea before, and why
didn’t any modern browser do this? Is there enough value
to devote engineering resource?<br>
</li>
<li>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?</li>
</ol>
<p><br>
</p>
<p>What do you think?<br>
</p>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Mar 19, 2016 at 12:00 AM,
Brunoais <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:brunoaiss@gmail.com" target="_blank">brunoaiss@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> I think the idea
was mentioned like this:<br>
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. <br>
<br>
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.<br>
<br>
If you are open for it, I'm open to propose a use-case
on how to get those kinds of results.
<div>
<div><br>
<br>
<div>On 18-03-2016 10:20, Gijs Kruitbosch wrote:<br>
</div>
<blockquote type="cite">
<div>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 <a
moz-do-not-send="true"
href="http://www.mydatingsite.com"
target="_blank">www.mydatingsite.com</a> 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.<br>
<br>
~ Gijs<br>
<br>
On 18/03/2016 05:07, Matthew N. wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">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.<br>
<br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">CC'ing
mozilla.dev.tech.network to see what the
Necko team has to say about whether we can
support this in Firefox yet.<br>
<br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Matthew
N. (:MattN)<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Mar 17, 2016
at 9:29 PM, Bram Pitoyo <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:bram@mozilla.com"
target="_blank">bram@mozilla.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>If a URL is loaded when there’s
no internet connection, Firefox will
throw an error page, as expected.<br>
<br>
</div>
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.<br>
<br>
The result:<br>
<ul>
<li>I know that my internet is back
on because Firefox now shows the
page I had failed to load</li>
<li>I save a little bit of time by
not needing to click “Reload” or
hit Ctrl+R<br>
</li>
</ul>
</div>
Have we thought of a behaviour like
this?<br>
</div>
<br>
_______________________________________________<br>
firefox-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:firefox-dev@mozilla.org"
target="_blank">firefox-dev@mozilla.org</a><br>
<a moz-do-not-send="true"
href="https://mail.mozilla.org/listinfo/firefox-dev"
rel="noreferrer" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
firefox-dev mailing list
<a moz-do-not-send="true" href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>
<a moz-do-not-send="true" href="https://mail.mozilla.org/listinfo/firefox-dev" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a>
</pre>
</blockquote>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
firefox-dev mailing list
<a moz-do-not-send="true" href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>
<a moz-do-not-send="true" href="https://mail.mozilla.org/listinfo/firefox-dev" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
firefox-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a><br>
<a moz-do-not-send="true"
href="https://mail.mozilla.org/listinfo/firefox-dev"
rel="noreferrer" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>