Closed
Bug 915660
Opened 11 years ago
Closed 10 years ago
[User Story] Hide Offline Error Screen When Connectivity Resumes - App Background
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(feature-b2g:2.0)
People
(Reporter: pdol, Assigned: albert)
References
Details
(Keywords: feature, Whiteboard: [ucid:System57, 1.4:P2, ft:systemsfe][systemsfe])
User Story: As a user who currently has a launched app background with an offline error screen showing, when network connectivity resumes, I want the error screen to disappear and the current app page to reload at the point when the app is moved to the foreground so that I can continue using the app without having to relaunch it. Acceptance Criteria: 1. If I have an app in the background with the offline error screen showing (not visible since it is background) (as in System53/54/55), when the app is moved to the foreground and my device has data connectivity, the error screen is no longer showing and the app page is reloaded (equivalent to the previous "Try Again" button). 2. If I have an app in the background with the offline error screen showing (not visible since it is background) (as in System53/54/55) and my device resumes data connectivity, the app page is not reloaded while it remains in the background. 3. If I have an app in the background with the offline error screen showing (not visible since it is background) (as in System53/54/55), but the error was due to a form submission, HTTP post or equivalent, when the app is moved to the foreground and my device has data connectivity, I am asked to reload the page again (TBD by UX).
Updated•11 years ago
|
Whiteboard: [ucid:System57] → [ucid:System57][systemsfe]
Updated•11 years ago
|
Blocks: 1.3-systems-fe
Updated•11 years ago
|
Whiteboard: [ucid:System57][systemsfe] → [ucid:System57][systemsfe][1.3:p2]
Updated•11 years ago
|
Whiteboard: [ucid:System57][systemsfe][1.3:p2] → [ucid:System57][systemsfe]
Comment 1•11 years ago
|
||
Mike - Is this fixed with the landing of the blue offline error page?
Flags: needinfo?(mhenretty)
Updated•11 years ago
|
No longer blocks: 1.3-systems-fe
Reporter | ||
Updated•11 years ago
|
Whiteboard: [ucid:System57][systemsfe] → [ucid:System57, 1.4:P2, ft:systemsfe]
Updated•11 years ago
|
Blocks: 1.4-systems-fe
Updated•10 years ago
|
Flags: in-moztrap?(rafael.marquez)
Updated•10 years ago
|
Assignee: nobody → crdlc
Target Milestone: --- → 1.4 S1 (14feb)
Updated•10 years ago
|
Whiteboard: [ucid:System57, 1.4:P2, ft:systemsfe] → [ucid:System57, 1.4:P2, ft:systemsfe][systemsfe]
Updated•10 years ago
|
Target Milestone: 1.4 S1 (14feb) → 1.4 S2 (28feb)
Updated•10 years ago
|
blocking-b2g: --- → 1.4?
Updated•10 years ago
|
blocking-b2g: 1.4? → ---
Updated•10 years ago
|
No longer blocks: 1.4-systems-fe
Updated•10 years ago
|
Flags: in-moztrap?(rafael.marquez)
Updated•10 years ago
|
Blocks: 2.0-systems-fe
Updated•10 years ago
|
Target Milestone: 1.4 S2 (28feb) → 1.4 S3 (14mar)
Comment 4•10 years ago
|
||
Changing to Albert because the only pending bug is assigned to him
Assignee: crdlc → acperez
Updated•10 years ago
|
Target Milestone: 1.4 S3 (14mar) → 1.4 S4 (28mar)
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
QA Contact: rafael.marquez
Updated•10 years ago
|
feature-b2g: --- → 2.0
Updated•10 years ago
|
Flags: in-moztrap?(rafael.marquez)
You need to log in
before you can comment on or make changes to this bug.
Description
•