1131837 - [Dialer] Tapping the call log edit button activates the missed tab

Status: RESOLVED DUPLICATE of bug 1131695

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

Description

[KTucker [:KTucker][Inactive 3/4/2016]]

Description:
When the user taps on the "Edit" button while in the call long, they will notice that the "Missed" tab will sometimes be activated instead.

Repro Steps:
1) Update a Flame to 20150210010523
2) Open the dialer app. 
3) Tap on the "Call Log" icon.
4) Tap towards the bottom of the "Edit" button and observe.

Actual:
Instead of going into "Edit" mode, the user will be taken to the missed call log.

Expected:
Tapping on the "Edit" button does not activate the "Missed Call" tab.

Environmental Variables:
Device: Flame 3.0 (Full Flash)(KK)(319mb)
Build ID: 20150210010523
Gaia: 0cf517083f7eb5fc269e1236edba50534f65e3cd
Gecko: 2cb22c058add
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 38.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

Repro frequency: 5/5
See attached: Video, Logcat

Comment 1

[KTucker [:KTucker][Inactive 3/4/2016]]

Attachment: EditMissedLog.txt

Comment 2

[KTucker [:KTucker][Inactive 3/4/2016]]

I do not know if this 100% reproduces on Flame 2.2 because I am blocked by bug 1131695

The "Edit" button when tapped will indicate to the user that it was tapped but doesn't do anything.

Environmental Variables:
Device: Flame 2.2
BuildID: 20150210002516
Gaia: b30c8e4303595a0fcb5b640d673cf8503b954701
Gecko: 3e9fa4e70a1b
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 37.0a2 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

-------------------------------------------------------

I could not reproduce this issue on the Flame 2.1

Edit mode was always activated when tapping on the "Edit" button.

Environmental Variables:
Device: Flame 2.1 (Full Flash)(KK)(319mb)
BuildID: 20150210002200
Gaia: 7dd130a312f12c89b2d41948f8557effa56afbf6
Gecko: 2de03dfa9aac
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 34.0 (2.1) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Comment 3

[Peter Bylenga [:PBylenga]]

[Blocking Requested - why for this release]:
Functional regression with high visibility.

QAWanted to check the last working build identified in the Window for bug 1131695 to see if we can identify the affected status for 2.2 on this issue.  Will move b2g-blocking nom to 2.2? if it does reproduce.

Comment 4

[Brogan Zumwalt [Inactive]]

B2G-Inbound Regression Window:

Last working B2G-Inbound build:
Device:  Flame 3.0
BuildID: 20150203043327
Gaia: ed2b99f7ba4a4517d0aa7d08b9f3d783181acd9a
Gecko: 60ff87d49efb
Version: 38.0a1 (3.0)
Firmware: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

First broken B2G-Inbound build:
Device: Flame 3.0
Build ID: 20150203063725
Gaia: 9093ccc0c909c6977bbaaf570c0728bc12d75a3d
Gecko: ea24223ba980
Version: 38.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0


Working Gaia with Broken Gecko issue does NOT reproduce:
Gaia: ed2b99f7ba4a4517d0aa7d08b9f3d783181acd9a
Gecko: ea24223ba980

Working Gecko with Broken Gaia issue DOES reproduce:
Gaia: 9093ccc0c909c6977bbaaf570c0728bc12d75a3d
Gecko: 60ff87d49efb


B2G-Inbound Pushlog:
https://github.com/mozilla-b2g/gaia/compare/ed2b99f7ba4a4517d0aa7d08b9f3d783181acd9a...9093ccc0c909c6977bbaaf570c0728bc12d75a3d


This issue appears to occur due to changes made in bug 1128672

Comment 5

[KTucker [:KTucker][Inactive 3/4/2016]]

Etienne, can you take a look at this please? Looks like the landing for bug 1128672 might have caused this to occur.