Closed
Bug 1197965
Opened 11 years ago
Closed 8 years ago
[Contacts] Unable to scroll up when holding over the X button of a field.
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect)
Tracking
(tracking-b2g:backlog, b2g-v2.2 affected, b2g-master affected)
RESOLVED
WONTFIX
| tracking-b2g | backlog |
People
(Reporter: jthomas, Unassigned)
Details
(Whiteboard: [2.5-Daily-Testing][Spark])
Attachments
(1 file)
|
301.73 KB,
text/plain
|
Details |
Description:
If the user begins filling out one of the various fills within a contact and then attempts to readjust the view of this field by scrolling up or down over the X button the field will be erased instead of scrolling as desired.
Note: This issue was found unintentionally as I was attempting to align the phone box and accidentally erased the information by attempting to scroll up too close by the X button.
Repro Steps:
1) Update a Aries to 20150824130451
2) Select Contacts > New Contact
3) Begin filling out a field such as Phone
4) Attempt to adjust the position by scrolling up or down over the X button.
Actual:
Contact field information is erased.
Expected:
Contact fields can be scrolled when press and holding over X button.
Environmental Variables:
Device: Aries 2.5 Kk
Build ID: 20150824130451
Gaia: d7fb5717d3e0153ac64af2c0d5c11079846d81c3
Gecko: 205427533c567b7b67bf2df3937e851f16204668
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 43.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0
User Impact: Information inserted in contact field is unintentionally erased.
Repro frequency: 5/5
See attached: Logcat & Video
Video coming as soon as YouTube acknowledges my upload.
| Reporter | ||
Comment 1•11 years ago
|
||
This issue DOES occur on Flame 2.5 and 2.1
Result: Contact field information is erased when attempting to scroll up or down near the X button.
Environmental Variables:
Device: Flame 2.5 Kk Fullflash (319mb)
BuildID: 20150824073143
Gaia: d7fb5717d3e0153ac64af2c0d5c11079846d81c3
Gecko: ba43a48d3c528cc956335793e02504e5ca2c149f
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0
Environmental Variables:
Device: Flame 2.2 Kk Fullflash (319mb)
BuildID: 20150821074640
Gaia: 335cd8e79c20f8d8e93a6efc9b97cc0ec17b5a46
Gecko: d29ec25e40e7
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.2:
--- → affected
status-b2g-master:
--- → affected
Flags: needinfo?(ktucker)
Whiteboard: [2.5-Daily-Testing][Spark]
Comment 2•11 years ago
|
||
On iPhone and Android, the action is not initiated until the user removes their finger. Johan, can you take a look at this? It is not a regression but this could frustrate end users.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(jlorenzo)
Comment 3•11 years ago
|
||
Yeah, I agree. Usually you trigger action when the finger is released. As it's not a regression from 2.2, I don't think we can make this bug a blocker. Let's put it in the backlog for having a priority on it.
tracking-b2g:
--- → backlog
Flags: needinfo?(jlorenzo)
Comment 4•8 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•