Closed
Bug 598310
Opened 14 years ago
Closed 14 years ago
Make "Work Offline" more discoverable in the app button menu for users who need it to recover from Firefox going offline automatically
Categories
(Firefox :: Menus, defect)
Tracking
()
VERIFIED
FIXED
Firefox 4.0b7
Tracking | Status | |
---|---|---|
blocking2.0 | --- | beta7+ |
People
(Reporter: rcampbell, Assigned: dao)
References
Details
Attachments
(1 file)
1.92 KB,
patch
|
Gavin
:
review+
faaborg
:
ui-review+
|
Details | Diff | Splinter Review |
Move Work Offline to someplace else in the Firefox menu. Consider other menu items as well.
Reporter | ||
Updated•14 years ago
|
blocking2.0: --- → ?
Assignee | ||
Updated•14 years ago
|
Assignee | ||
Updated•14 years ago
|
OS: Mac OS X → Windows 7
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → dao
Summary: Audit contents of Web Developer menu → Make "Work Offline" more discoverable in the app button menu for users who need it to recover from Firefox going offline automatically
Assignee | ||
Comment 1•14 years ago
|
||
This adds Work Offline below Start Private Browsing and shows it only if Firefox is in offline mode, so it won't normally distract users.
Attachment #477581 -
Flags: ui-review?(faaborg)
Attachment #477581 -
Flags: review?(gavin.sharp)
Assignee | ||
Updated•14 years ago
|
Status: NEW → ASSIGNED
Version: unspecified → Trunk
Comment 2•14 years ago
|
||
I think this functionality should be ripped out of firefox entirely. What is the point of "Working Offline"? If the idea is to be able to use the cached pages, why not include a link (similar to google search) on the network error page to the cached version of the page if it exists. Further navigation (through links on the cached page) should be directed to the cache if available. Otherwise, back to the network error page. That seems so much simpler and straightforward than a "Work Offline" button that gets triggered on its own sometimes (and very annoyingly).
Updated•14 years ago
|
Attachment #477581 -
Flags: review?(gavin.sharp) → review+
Comment 3•14 years ago
|
||
Removing all support for "offline mode" isn't something that should be discussed here - file a new bug? It's certainly not feasible for 2.0.
Comment 4•14 years ago
|
||
Filed as bug 598719.
Comment 5•14 years ago
|
||
Comment on attachment 477581 [details] [diff] [review]
patch
This is an acceptable mitigation step for users who get accidentally trapped in offline mode due to a bug. However, we really need to in the future resolve those bugs and remove offline mode entirely. This shouldn't be considered a resolution to the overall problem.
Attachment #477581 -
Flags: ui-review?(faaborg) → ui-review+
Assignee | ||
Updated•14 years ago
|
Attachment #477581 -
Flags: approval2.0?
Updated•14 years ago
|
blocking2.0: ? → beta7+
Updated•14 years ago
|
Attachment #477581 -
Flags: approval2.0?
Assignee | ||
Comment 6•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 4.0b7
Comment 7•14 years ago
|
||
Verified fixed with Mozilla/5.0 (Windows NT 5.1; rv:2.0b8pre) Gecko/20101023 Firefox/4.0b8pre. A Litus test we be covered by bug 595610.
Status: RESOLVED → VERIFIED
Flags: in-litmus-
You need to log in
before you can comment on or make changes to this bug.
Description
•