Closed Bug 911328 Opened 10 years ago Closed 9 years ago

[User Story] Quickly Enable Connectivity When Airplane Mode Is On

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::System
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(feature-b2g:2.0)

Status:
VERIFIED FIXED
Milestone:
1.4 S4 (28mar)
Project Flags:
feature-b2g 2.0

People

(Reporter: pdol, Unassigned)

References

Details

(Keywords: feature, Whiteboard: [ucid:System53, 1.4:P2, ft:systemsfe][systemsfe]) 

User Story:

As a user who has airplane mode turned on and WiFi is disabled, instead of being shown the blue offline screen, I should be made aware that airplane mode is currently enabled and given a way to quickly turn off airplane mode so that I don’t need to manually leave the app, open the settings (or utility tray), turn off airplane mode and return to the app.


Acceptance Criteria:
1. If airplane mode is turned on and all data connections are disabled, in scenarios in which I would normally be shown the blue offline screen, I am informed that airplane mode is currently on.
2. After I am informed that airplane mode is currently on as in 1, I can turn off airplane mode without needing to access the settings or utility tray.
3. If I chose to turn off airplane mode, my connections are restored to their previous state (prior to enabling airplane mode).
4. If I chose to ignore the message received in 1, I am taken to the previous position in the app. (if one exists)
5. If I chose to ignore the message received in 1, and I am currently on the entry point within the app (ie. first screen), I am exited out of the app.
Assignee: nobody → mhenretty
This should be fixed as part of bug 882186.
Depends on: 882186
Peter Dolanjski deleted the linked story in Pivotal Tracker
Ghislain 'Aus' Lacroix changed story state to started in Pivotal Tracker
Whiteboard: [ucid:System53] → [ucid:System53][systemsfe]
blocking-b2g: --- → 1.3+
We certainly want this in 1.3, but we won't block on it.
blocking-b2g: 1.3+ → -
Target Milestone: --- → 1.3 Sprint 3 - 10/25
Blocks: 930630
Target Milestone: 1.3 Sprint 3 - 10/25 → 1.3 Sprint 4 - 11/8
Flags: in-moztrap?(jsmith)
Whiteboard: [ucid:System53][systemsfe] → [ucid:System53][systemsfe][1.3:p2]
Whiteboard: [ucid:System53][systemsfe][1.3:p2] → [ucid:System53][systemsfe]
Fixed per landing of bug 882186
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Actually they aren't - checked with mhenretty that this isn't fully fixed by bug 882186.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
No longer blocks: 1.3-systems-fe
Flags: in-moztrap?(jsmith) → in-moztrap?
Whiteboard: [ucid:System53][systemsfe] → [ucid:System53, 1.4:P2, ft:systemsfe]
Take myself off of this for now, as I might not be the one to work on it after all.
Assignee: mhenretty → nobody
Flags: in-moztrap? → in-moztrap?(rafael.marquez)
Whiteboard: [ucid:System53, 1.4:P2, ft:systemsfe] → [ucid:System53, 1.4:P2, ft:systemsfe][systemsfe]
Target Milestone: 1.3 Sprint 4 - 11/8 → 1.4 S2 (28feb)
blocking-b2g: - → 1.4?
blocking-b2g: 1.4? → ---
No longer blocks: 1.4-systems-fe
Flags: in-moztrap?(rafael.marquez)
Target Milestone: 1.4 S2 (28feb) → 1.4 S3 (14mar)
Target Milestone: 1.4 S3 (14mar) → 1.4 S4 (28mar)
closing as latest bug 969267 is finished
Status: REOPENED → RESOLVED
Closed: 10 years ago → 9 years ago
Resolution: --- → FIXED
QA Contact: rafael.marquez
Verified in master(v1.5) branch
Status: RESOLVED → VERIFIED
feature-b2g: --- → 2.0
Flags: in-moztrap?(rafael.marquez)
You need to log in before you can comment on or make changes to this bug.