Closed Bug 1023805 Opened 10 years ago Closed 6 years ago

[Flame][v1.4][Contacts] The prompt is display as “Export to SD card” during export contacts to internal storage

Categories

(Firefox OS Graveyard :: Gaia::Contacts, defect, P3)

Product:
Firefox OS Graveyard
Component:
Gaia::Contacts
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(tracking-b2g:backlog, b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)

Status:
RESOLVED WONTFIX
Project Flags:
tracking-b2g backlog
Tracking Flags:
Tracking Status
b2g-v1.4 --- affected
b2g-v2.0 --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: greatwall2686, Unassigned)

References

Details

(Whiteboard: torch, permafail)

Attachments

(1 file)

character error
173.14 KB, image/png
Details
Attached image character error — 
* Description:
The prompt is display as “Export to SD card” during export contacts to internal storage

* Reproduction steps:
  1. Set the default media location as “Internal”, and there is no SD card in device
  2. Go to contacts->edit->export contacts->memory card
3. Choose some contacts, then tap export
4. Check the loading screen

* Expected result:
  The prompt is “Export to internal storage”

* Actual result:
The prompt is display as “Export to SD card”

* Reproduction build: (Buri - Firefox OS V1.4 outside)
 - Gaia      17b102ee8d9a724b62285547cc5f1c5d30bfb01c
 - Gecko     https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/95be84248033
 - BuildID   20140520000201
 - Version   30.0

* Reproduction Frequency
  100%
Another problem related to bug 1019511 ,will block on that one, will be probably fix in 2.1
Depends on: 1019511
Status: UNCONFIRMED → NEW
status-b2g-v2.0: --- → affected
Ever confirmed: true
Flags: needinfo?(ktucker)
Whiteboard: torch → torch, [2.0-flame-test-run-2]
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
Flags: needinfo?(ktucker)
Whiteboard: torch, [2.0-flame-test-run-2] → torch, [2.0-flame-test-run-2], [2.0-flame-test-run-3]
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
status-b2g-v1.4: --- → affected
status-b2g-v2.1: --- → unaffected
Flags: needinfo?(ktucker)
Whiteboard: torch, [2.0-flame-test-run-2], [2.0-flame-test-run-3] → torch, permafail
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
status-b2g-v2.2: --- → affected
Flags: needinfo?(dharris)
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(dharris)
[Tracking Requested - why for this release]: This test case has failed for 3 releases (aka "permalfail"). Let's choose between putting a high priority on this bug, or removing the test case from Moztrap.
tracking-b2g: --- → backlog
Per comms triage
Priority: -- → P3
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: