Closed
Bug 996835
Opened 12 years ago
Closed 8 years ago
[B2G][Bluetooth] When tapping 'Continue' on a processing bluetooth file the user is returned to the homescreen
Categories
(Firefox OS Graveyard :: Gaia::Bluetooth, defect)
Tracking
(b2g-v1.3 affected, b2g-v1.3T affected, b2g-v2.0 affected)
RESOLVED
WONTFIX
People
(Reporter: dharris, Unassigned)
References
()
Details
(Whiteboard: 1.3tarakorun2, [2.0-flame-test-run-2])
Attachments
(1 file)
|
22.44 KB,
application/x-gzip
|
Details |
Description:
When the user is in the notification overlay and taps on the processing bluetooth file that they are export, they can either cancel or continue the file transfer. When the user taps on continue they are brought back to the home screen instead of back to the notification overlay
Prerequisites: Have bluetooth on, and paired to another device
Repro Steps:
1) Update a tarako to BuildID: 20140414004001
2) Go to Contacts app>Settings>Export>Bluetooth
3) Select a contact and tap Export
4) When prompted, select the paired device
5) Pull down the notification overlay
6) Select the processing bluetooth file
7) Tap continue
Actual:
The user is brought back to the home screen
Expected:
The user is brought back to the notifications overlay
1.3t Environmental Variables:
Device: tarako 1.3t
BuildID: 20140414004001
Gaia: 0e7f21e61625b75a9149480cd5a259211549f020
Gecko: 3b02811c314a
Version: 28.1
Firmware Version: sp6821
Keywords: Utility tray, Ok, background, closed, contacts, send
Repro frequency: 100%
Link to failed test case:9809 - https://moztrap.mozilla.org/manage/case/9809/
See attached: Logcat, Firewatch, Video - http://www.youtube.com/watch?v=9hqe4pUO1NM&feature=youtu.be
| Reporter | ||
Comment 1•12 years ago
|
||
This issue also occurs on the buri on the latest 1.3
1.3 Environmental Variables:
Device: buri 1.3 MOZ
BuildID: 20140414004002
Gaia: 8b92c56267fe50772095f1f25d6cc1f9c9966eb4
Gecko: 3e26908fca71
Version: 28.0
Firmware Version: v1.2-device.cfg
status-b2g-v1.3T:
--- → affected
Updated•12 years ago
|
status-b2g-v1.3:
--- → affected
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → affected
Flags: needinfo?(ktucker)
Whiteboard: 1.3tarakorun2 → 1.3tarakorun2, [2.0-flame-test-run-2]
Updated•11 years ago
|
Flags: needinfo?(ktucker)
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Comment 2•11 years ago
|
||
(In reply to dharris from comment #0)
> Actual:
> The user is brought back to the home screen
>
Because z-index limitation for showing the confirm dialog, we have to hide notification overlay first. If we want to go back to notification overlay, it is required to show again. Not a blocking issue, but it's better to need info. UX team for the expected result here.
> Expected:
> The user is brought back to the notifications overlay
Flags: needinfo?(ofeng)
Comment 3•11 years ago
|
||
As I know, after tapping any notification on the notification tray, the notification tray should dismiss. It's by design. Is that right, Rob?
Flags: needinfo?(ofeng) → needinfo?(rmacdonald)
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Comment 4•11 years ago
|
||
(In reply to Omega Feng [:Omega] from comment #3)
> As I know, after tapping any notification on the notification tray, the
> notification tray should dismiss. It's by design. Is that right, Rob?
That is correct, Omega. Looking at the video, though, the flow still seems to be missing some indicators that might be helpful. I'd suggest sync'ing with Francis for any transfer related patterns. Although bluetooth transfers are quicker, banners to indicate that the transfer has started/completed should be considered.
Flags: needinfo?(rmacdonald) → needinfo?(fdjabri)
Comment 5•11 years ago
|
||
FYI, The download manager specs are available at: https://mozilla.box.com/s/5q5rehaw2z2kgyeag43n
Flags: needinfo?(fdjabri)
Comment 6•8 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•