598719 - Replace "work offline" functionality with better cache navigation mechanism

Status: RESOLVED INACTIVE

(Core :: General, enhancement)

Description

[Nochum Sossonko [:Natch]]

See bug 598310 comment 2, I'm filing this bug as per bug 598310 comment 3.

I think a cache navigation mechanism accessible through either a new "cache:" protocol and visible in the ui on the network error page is far more productive than the automatic "work offline" detection, etc.

Comment 1

[Luke Iliffe (Harlequin99)]

Bug 565564 is about removing the work offline code, although it is more of a discussion than a bug at the moment. Perhaps change the title of this bug to just your proposed cache changes, this could then depend on bug 565564

Comment 2

[Nochum Sossonko [:Natch]]

(In reply to comment #1)
Good point, done. Although, I put this in the blocking field since removing the "work offline" functionality really depends on replacing it with something better first...

Comment 3

[Ben Bucksch (:BenB)]

Please note that there are also HTML5 "offline web applications" that can explicitly check for the offline state. (wasn't my idea!)

Comment 4

[Nochum Sossonko [:Natch]]

(In reply to comment #3)
The core api can remain, it's the Application's usage that we want to remove.

Firefox detects the offline state and will go into an "offline mode" where pages are served up from the cache if available or the user is directed to the offline page. This (as well as manually going into the "offline mode") should be removed in favor of this bug's request...

Comment 5

[vitar]

(In reply to Nochum Sossonko [:Natch] from comment #4)
> Firefox detects the offline state and will go into an "offline mode"...

Very often this detection is broken because a host system have some always-online net ifaces -- TUN/TAP, VM bridges etc. etc. -- so I personally prefer to switch on-/offline modes by self and only when I need it.

But main idea abt "better navigation" is good.