1017961 - [Flame][v1.4][Contacts]The progress bar is still in loading status when delete the first mobile number in contact edit page.

Status: RESOLVED WORKSFORME

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

Description

[greatwall2686]

* Description: The progress bar is still in loading status when delete the first mobile number in contact edit page. Then cancel the edit, the number is still exist. But go into edit page, the number is disappeared.(VID_20140530_105545)

* Reproduction steps:
  1. Open the contact app
  2. Choose a contact which save more than 2 mobile phone
  3. Go into the contact edit page
  4. Tap the fork button to delete the first mobile phone’s number
  5. Update the edit page

* Expected result:
  The first mobile phone’s number delete successfully

* Actual result:
  The progress bar is still in loading status, and the number can’t deleted

* 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
  - 10/10

Comment 1

[greatwall2686]

Attachment: VID_20140530_105545.zip

Comment 2

[Jason Smith [:jsmith]]

QA Wanted to check 1.3.

Comment 3

[Yeojin Chung [:YeojinC]]

This issue does NOT occur on the Flame 1.3 Base Image:

Environmental Variables:
Device: Flame 1.3
Build ID: 20140520094859
Gaia: a73235d23685e9898f40647cebd83b3fcbfd0117
Gecko: b637b0677e15318dcce703f0358b397e09b018af
Version: 28.0 (1.3) 
Firmware Version: v10G-2

Comment 4

[Jason Smith [:jsmith]]

Can we confirm this on the latest 1.4?

Comment 5

[Dean R. Gomez (DeanG)]

This issue DOES NOT occur on Flame 1.4

1.4 Environmental Variables:
Device: Flame 1.4
Build ID: 20140611000202
Gaia: d1cf95dc5e8b2f52148487291318542f1396608e
Gecko: a8bb6b76696b
Version: 30.0 (1.4) 
Firmware Version: v10G-2

Comment 6

[Jason Smith [:jsmith]]

Joshua - If the bug no longer reproduces on the latest build, you should mark the bug as works for me.

Comment 7

[Joshua Mitchell (Inactive)]

Right you are! I miss-read the issue as written up in 2.0 and not occurring in 1.4 but that is not the case. It is written-up for 1.4 but no longer occurring in the latest 1.4

Marking as works-for-me