Closed
Bug 999501
Opened 11 years ago
Closed 10 years ago
"Export error" messages when user exports contact via Bluetooth
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect, P3)
Tracking
(tracking-b2g:backlog, b2g-v1.4 affected, b2g-v2.0 affected)
RESOLVED
WORKSFORME
| tracking-b2g | backlog |
People
(Reporter: lolimartinezcr, Unassigned, Mentored)
Details
(Whiteboard: [good first bug])
Attachments
(2 files)
Tested
1.4
Hamachi
Gecko 53aec4a
Gaia 2643291
Reproducible 100%
STR
1. Tap contact aplication.
2. Tap settings.
3. Tap "Export contacts".
4. Tap Bluetooth.
5. Select all
6. Tap Export button.
7. Appear all devices in the area.
8. Tap "X" button (close button)
Actual result:
Export error screen
Expected result:
Go back last page.
Comment 1•11 years ago
|
||
Hi,
It also occurs with 4/22 master build:
Device: Hamachi
BuildId: 20140422065611
Gecko: 22b3e73
Gaia: f046370
Platform version: 31.0a1
Regarding UX spec, please refer to https://mozilla.app.box.com/s/cpwxyeisjurklut93f0a/1/1030018334/9847129304/1, page 7, tapping on "X" from "Bluetooth Devices" screen (see BT_devices.png screenshot) should return to "Export Contacts" screen instead of showing the current error page (2014-04-23-master.png)
Comment 2•11 years ago
|
||
Comment 3•11 years ago
|
||
ni to Carrie to confirm the expected flow. Adding to backlog to be properly prioritized. Thanks!
blocking-b2g: --- → backlog
status-b2g-v1.4:
--- → affected
status-b2g-v2.0:
--- → affected
Flags: needinfo?(cawang)
Summary: "Export error" messages when user exports contact via Bluethoot → "Export error" messages when user exports contact via Bluetooth
Comment 5•11 years ago
|
||
This is not a critical bug for any specific release- its open to be fixed when we have time.
| Assignee | ||
Updated•11 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Updated•10 years ago
|
Priority: -- → P3
Whiteboard: [good first bug]
Updated•10 years ago
|
Mentor: francisco
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•