> Mobile people with laptops frequently transition between
> online and offline. It's stupid to have to manually tell Firefox when this is
> happening when the system already knows.
ok, I understand and accept this use case
Then we have two different situations, which require two different switches in the UI.
> We don't reload all pages when changing online/offline state.
that's exactly the problem I'm referring to here. When firefox goes online again I have to reload all relevant pages manually, because cache contents doesn't help me in many cases (think of bug-trackers, bank accounts, etc.).
So, in my use case (always wanting to be online with unwanted interruptions) firefox should inform me when failing to load a page and should NOT go offline but instead should try to load the missing page again when the connection comes back. In this case the "WANT a connection" state is relevant and after that also the "HAVE a connection" state.
so we have four situations:
connection firefox
WANT HAVE action
x x load page from net
x - wait for connection, perhaps load page from cache and inform user
- x load page from cache?
- - load page from cache
the WANT state could be the inverted offline flag in firefox
> Mobile people with laptops frequently transition between
> online and offline. It's stupid to have to manually tell Firefox when this is
> happening when the system already knows.
ok, I understand and accept this use case
Then we have two different situations, which require two different switches in the UI.
> We don't reload all pages when changing online/offline state.
that's exactly the problem I'm referring to here. When firefox goes online again I have to reload all relevant pages manually, because cache contents doesn't help me in many cases (think of bug-trackers, bank accounts, etc.).
So, in my use case (always wanting to be online with unwanted interruptions) firefox should inform me when failing to load a page and should NOT go offline but instead should try to load the missing page again when the connection comes back. In this case the "WANT a connection" state is relevant and after that also the "HAVE a connection" state.
so we have four situations:
connection firefox
WANT HAVE action
x x load page from net
x - wait for connection, perhaps load page from cache and inform user
- x load page from cache?
- - load page from cache
the WANT state could be the inverted offline flag in firefox