If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[User Story] Hide Offline Error Screen When Connectivity Resumes - App Background

VERIFIED FIXED in 1.4 S4 (28mar)

Status

Firefox OS
Gaia::System
VERIFIED FIXED
4 years ago
3 years ago

People

(Reporter: pdol, Assigned: albert)

Tracking

(Blocks: 1 bug, {feature})

unspecified
1.4 S4 (28mar)
ARM
Gonk (Firefox OS)
feature
Dependency tree / graph
Bug Flags:
in-moztrap ?

Firefox Tracking Flags

(feature-b2g:2.0)

Details

(Whiteboard: [ucid:System57, 1.4:P2, ft:systemsfe][systemsfe])

(Reporter)

Description

4 years ago
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).
(Reporter)

Updated

4 years ago
Blocks: 930630

Updated

4 years ago
Whiteboard: [ucid:System57] → [ucid:System57][systemsfe]

Updated

4 years ago
Blocks: 923441
Whiteboard: [ucid:System57][systemsfe] → [ucid:System57][systemsfe][1.3:p2]
Whiteboard: [ucid:System57][systemsfe][1.3:p2] → [ucid:System57][systemsfe]
Mike - Is this fixed with the landing of the blue offline error page?
Flags: needinfo?(mhenretty)
Not fixed.
Flags: needinfo?(mhenretty)

Updated

4 years ago
No longer blocks: 923441
(Reporter)

Updated

4 years ago
Whiteboard: [ucid:System57][systemsfe] → [ucid:System57, 1.4:P2, ft:systemsfe]

Comment 3

4 years ago
Moving to Gaia::System
Component: Gaia::E-Mail → Gaia::System
Blocks: 943819
Depends on: 964724
Depends on: 967401
Depends on: 967402

Updated

4 years ago
Flags: in-moztrap?(rafael.marquez)
Assignee: nobody → crdlc
Target Milestone: --- → 1.4 S1 (14feb)
Whiteboard: [ucid:System57, 1.4:P2, ft:systemsfe] → [ucid:System57, 1.4:P2, ft:systemsfe][systemsfe]
Target Milestone: 1.4 S1 (14feb) → 1.4 S2 (28feb)
blocking-b2g: --- → 1.4?

Updated

4 years ago
blocking-b2g: 1.4? → ---

Updated

4 years ago
No longer blocks: 943819

Updated

4 years ago
Flags: in-moztrap?(rafael.marquez)
Blocks: 977007
Target Milestone: 1.4 S2 (28feb) → 1.4 S3 (14mar)
Changing to Albert because the only pending bug is assigned to him
Assignee: crdlc → acperez
Target Milestone: 1.4 S3 (14mar) → 1.4 S4 (28mar)
(Assignee)

Updated

4 years ago
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED

Updated

4 years ago
QA Contact: rafael.marquez

Comment 5

4 years ago
US verified in master branch (v1.5)
Status: RESOLVED → VERIFIED
feature-b2g: --- → 2.0

Updated

3 years ago
Flags: in-moztrap?(rafael.marquez)
You need to log in before you can comment on or make changes to this bug.