Closed
Bug 1193563
Opened 9 years ago
Closed 7 years ago
[Dialer] Repeatedly tapping on a call log entry initiates multiple calls
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(tracking-b2g:backlog, b2g-v2.2 affected, b2g-master affected)
RESOLVED
WONTFIX
| tracking-b2g | backlog |
People
(Reporter: KTucker, Unassigned)
References
()
Details
(Whiteboard: [2.5-Daily-Testing][Spark])
Attachments
(1 file)
|
(deleted),
text/plain
|
Details |
If the user repeatedly taps on a call log entry, they will notice several calls will be initiated to that particular number.
Repro Steps:
1) Update a Aries to 20150811152431
2) Open the "Dialer".
3) Tap on the call log icon.
4) At a rapid rate, repeatedly tap on a call log entry.
5) Pay close attention to the call screen.
Actual:
The phone will make multiple calls to that number.
Expected:
The device only initiates one call to that number when tapping on a call log entry.
Notes:
Environmental Variables:
Device: Aries 2.5 (Full Flash)(KK)(319mb)
Build ID: 20150811152431
Gaia: 9a8880a95ee4a4aea7895d4e2bcab31bc49ea281
Gecko: d82b5a78686a4f6630128fa7b999e0e343a9ef06
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:
Repro frequency: 5/5 100%
See attached: video clip, logcat
|
Reporter | |
Comment 1•9 years ago
|
||
This issue also reproduces on Flame Master and Flame 2.2
The user can initiates multiple calls to a call log entry by rapidly tapping on it.
Device: Flame 2.5 (Full Flash)(KK)(319mb)
BuildID: 20150811030209
Gaia: 9a8880a95ee4a4aea7895d4e2bcab31bc49ea281
Gecko: 8cba870a352c
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
Device: Flame 2.2 (Full Flash)(KK)(319mb)
Build ID: 20150811032503
Gaia: 102f1299e9eafe3760e1deb44d556b5c4f36b5af
Gecko: 13c447ed929e
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
status-b2g-v2.2:
--- → affected
status-b2g-master:
--- → affected
Whiteboard: [2.5-Daily-Testing][Spark]
|
|
Reporter | |
Comment 2•9 years ago
|
||
|
|
Reporter | |
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
|
|
Reporter | |
Updated•9 years ago
|
|
||
Comment 4•9 years ago
|
||
NI component owner to take a look, perhaps we should disable the button after first tap.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga) → needinfo?(jlorenzo)
That's a an edge that might happen in real life. Too edgy for being a blocker. Let's backlog it.
I agree on the solution proposed. Gabriele, do we have an easy way to mute the touch events once a call is started?
tracking-b2g:
--- → backlog
Flags: needinfo?(jlorenzo) → needinfo?(gsvelto)
|
||
Comment 6•9 years ago
|
||
Yes, it should be fairly straightforward to fix this.
Flags: needinfo?(gsvelto)
|
|
||
Comment 7•9 years ago
|
||
OK, the fix is rather easy but to handle corner cases correctly (e.g. a call failing to go through) we must first fix bug 1147735 so blocking on that one.
Depends on: 1147735
|
|
||
Updated•9 years ago
|
|
||
Comment 8•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•