Closed Bug 1060538 Opened 11 years ago Closed 10 years ago

[SMS] Tapping a number to edit it moves it to the back of the list

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected)

RESOLVED DUPLICATE of bug 1074131
Tracking Status
b2g-v1.4 --- affected
b2g-v2.0 --- affected
b2g-v2.1 --- affected

People

(Reporter: rpribble, Unassigned)

References

()

Details

(Whiteboard: [2.1-flame-test-run-1])

Attachments

(1 file)

Attached file Logcat.txt
Description: If the user has more than one phone number in the "To:" field of a text message and taps one of the numbers to edit it, the number will be moved automatically to the back of the list. This is very confusing to the user. It can appear that the device is changing the phone number rather than flipping the positions, and makes it difficult for the user to manipulate if they want the contacts listed in a certain order. Repro Steps: 1) Update a Flame device to BuildID: 20140829040202 2) SMS > Create new message > Tap "To:" field 3) Enter a few numbers, tap ';', enter a few more numbers, tap ';' again so the user will have entered two individual phone numbers 4) Tap the first phone number as if to edit it Actual: Tapping a phone number to edit it automatically flips it to the back of the list. Expected: User is able to edit phone numbers at their current position in the list. Environmental Variables: Device: Flame 2.1 Master (319MB) BuildID: 20140829040202 Gaia: 007f3c50cf69f044628a23c2376c6d88aa45f617 Gecko: d697d649c765 Version: 34.0a1 (2.1 Master) Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0 Notes: Repro frequency: 100% See attached: Video, logcat
This issue also occurs on the Flame v2.1 (512MB), Flame v2.0 (319MB), Flame v1.4 (318MB), Open_C v2.1, Open_C v2.0, and Open_C v1.4. Device: Flame Master (512mb) Build ID: 20140829040202 Gaia: 007f3c50cf69f044628a23c2376c6d88aa45f617 Gecko: d697d649c765 Version: 34.0a1 (Master) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Flame 2.0 (319mb) BuildID: 20140829000203 Gaia: 5bf3b8cdea15e62ce7bf77a15085a18e24e33c44 Gecko: 5bcf98ed9885 Version: 32.0 (2.0) Firmware: v123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Device: Flame 1.4 (319mb) Build ID: 20140829063010 Gaia: d6a1e9366dfcf9dd3d84661338996cb36b9a7e00 Gecko: 6de69ed3c146 Version: 30.0 (1.4) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Device: Open_C Master Build ID: 20140829040202 Gaia: 007f3c50cf69f044628a23c2376c6d88aa45f617 Gecko: d697d649c765 Version: 34.0a1 (Master) Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Open_C 2.0 BuildID: 20140829000203 Gaia: 5bf3b8cdea15e62ce7bf77a15085a18e24e33c44 Gecko: 5bcf98ed9885 Version: 32.0 (2.0) Firmware: v123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Device: Open_C 1.4 BuildID: 20140829063010 Gaia: d6a1e9366dfcf9dd3d84661338996cb36b9a7e00 Gecko: 6de69ed3c146 Version: 30.0 (1.4) Firmware: P821A10v1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Tapping a phone number to edit it automatically flips it to the back of the list. It is very confusing to the user.4
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard tag is missing here and the tracking flags need to be updated.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(rpribble)
Whoops, corrected.
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
Flags: needinfo?(rpribble) → needinfo?(ktucker)
Whiteboard: [2.1-flame-test-run-1]
This is probably by design but I have to agree with the tester here that this is confusing functionality. Not nominating to block on this since it is probably a design decision and not a regression.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
It's not really by design, it was just easier that way. I really think we should work using the recipient index, we have other edge-casy issues because of this.
Duping to bug 1074131 that has a little more information from our former UX designer.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: