Closed
Bug 820156
Opened 13 years ago
Closed 12 years ago
[Contacts] Show message to indicate that SIM Contacts import is not available when SIM is not inserted
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: maat, Assigned: jmcf)
References
Details
(Whiteboard: interaction [UX-P3])
Attachments
(1 file, 2 obsolete files)
206.27 KB,
image/jpeg
|
Details |
**PATH a**
start FTU with no SIM in phone:
1) select language
2) connect to Wifi network
...or...
**PATH b**
With no SIM inserted in the phone after FTU..
1) select contacts icon in tray at bottom of home screen
2) select import contacts icon in the top left hand corner of contact list header
**Expected**
1) import from SIM CTA is disabled
2) below disabled CTA is an orientation message stating: "Insert SIM card to import contacts from SIM"
**Actual**
1) import from SIM CTA is disabled
2) orientation message below disabled CTA is missing
Reporter | ||
Updated•13 years ago
|
Whiteboard: interaction [UX-P3]
When there's no SIM card is inserted the "Import from SIM" button will be disabled and a message will be shown underneath to give more information.
The import contacts screen displayed during the First Time User Experience is not correct. In order to be consistent the layout and components used should be the same as in the Contact Settings Screen accessible within the Contacts app.
Attachment #699254 -
Attachment is obsolete: true
Attachment #699261 -
Attachment is obsolete: true
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → jmcf
Status: NEW → ASSIGNED
Assignee | ||
Updated•12 years ago
|
Summary: [Contacts] Oriention messaging needed for when user wishes to import contacts from SIM, but not SIM card is inserted → [Contacts] Show message to indicate that SIM Contacts import is not available when SIM is not inserted
Assignee | ||
Comment 4•12 years ago
|
||
this bug was fixed weeks ago by another one.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•