[Dialer] 'Add to existing contact' and 'Create new contact' options are not conveniently located on the contextual menu when long-pressing on an 'unknown' phone number in the Call log.

RESOLVED WONTFIX

Status

P3
normal
RESOLVED WONTFIX
4 years ago
8 months ago

People

(Reporter: jmitchell, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(tracking-b2g:backlog, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)

Details

(Whiteboard: [3.0-Daily-Testing])

(Reporter)

Description

4 years ago
Description:
When in the dialer app call log user's would expect that long-pressing on an unknown contact would bring up a list of options that would include adding a new or updating a contact. In past versions this was true but now the only contextual menu options are to 'Send Message' or 'Call Information'. The desired options are found further in under the Call Information results but this seems counter-intuitive. Users would not expect those options to be there, as 'Call Information' only connotate information such as call duration and date.
Adding a new contact is typically a 'less buried' function on other market devices. On my Android ZTE Savvy there is no contextual menu but there is an icon dedicated to + contact that is always top-level information in the call log. 


Repro Steps:
1) Update a Flame to 20150114010205
2) Launch the dialer app.
3) Propagate the call log with an unknown number. 
4) Long press on that number

Actual:
Create new contact and add to existing contact options not present on top level contextual menu.

Expected:
These valuable options will be present on this menu. (At least present on both levels of menu).

Environmental Variables:
Device: Flame Master
Build ID: 20150114010205
Gaia: e2a0f7c311119d4a8e160bdfb9e28a0e61a180fc
Gecko: 63006936ab99
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 38.0a1 (Master)
Firmware Version: V18d-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

Repro frequency: 6/6
See attached: none
-----------------------------------------------------------------------------------------
This also occurs on 2.2 (V18d-1), 2.2 (V18d), and 2.1 (V18d-1)


Device: Flame 2.2 (KK - Nightly - Full-Flashed)
Build ID: 20150114002502
Gaia: 7c5b27cad370db377b18a742d3f3fdb0070e899f
Gecko: 748b20315f75
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 37.0a2 
Firmware Version: V18d-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Device: Flame 2.2 (KK - Nightly - Full-Flashed)
Build ID: 20150114002502
Gaia: 7c5b27cad370db377b18a742d3f3fdb0070e899f
Gecko: 748b20315f75
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 37.0a2
Firmware Version: V18d
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Device: Flame 2.1 (KK - Nightly - Full-Flashed)
Build ID: 20150113001255
Gaia: 836e6d74cb8b7016df555f85445893b3ff9aac12
Gecko: 074f79a929d2
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 34.0 (2.1)
Firmware Version: V18d-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
------------------------------------------------------------------------------------
This issue does NOT repro on 2.0 

Actual Results: Contextual menu contains 'Send Message', 'Create new contact' and 'Add to existing contact' options. (Probably not a regression but instead a design change implemented when 'Call Information' was added)

Device: Flame 2.0 (KK - Nightly - Full-Flashed)
Build ID: 20150113000203
Gaia: 31d6c9422cd0a8213df9f96019c9ab7168ec3ab3
Gecko: c6fd5db59e0e
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 32.0 (2.0)
Firmware Version: V18d-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
(Reporter)

Updated

4 years ago
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
NI on component owner for nomination decision and assignment.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga) → needinfo?(jlorenzo)
This was designed that way by UX (see bug 877971, attachment 8463237 [details]). If you think we should keep these 2 entries in the contextual window, do not hesitate to reopen this bug.
Blocks: 877971
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(jlorenzo)
Resolution: --- → INVALID
NI for UX input, with the design change we eliminated the shortest route for these actions.  Also it's not intuitive that they are behind "call information", our first thought was that they were missing.
Flags: needinfo?(cawang)
Hi, 

Actually I have a plan to refine the context menu and the call info page here. However, we are currently exploring the opportunities for the future FxOS. So I'd like to change the design after we have the idea of what we are going to do for V3 and fix it accordingly. Thanks!
Flags: needinfo?(cawang)
Reopening this bug as a future version might fix the issue.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Suggest to put this in backing.
Another question: Is dialer team using tracking-b2g for backlog? Or the blocking-b2g=backlog?
tracking-b2g: --- → ?
Flags: needinfo?(drs)
Flags are used by EPM and product. Internally to the Dialer team, we use the "dialer-most-wanted" metabug to track bugs that we want fixed.

In this case, this is a UX improvement. Thus, I would put this in both feature-b2g:backlog and ux-b2g, neither of which I have permission to set.
Flags: needinfo?(drs)
No longer blocks: 877971
See Also: → bug 877971
NI Wesley for setting correct flag.
Flags: needinfo?(whuang)
It would be great if tracking-b2g:backlog can be used as a universal flag for "backlog" items.
Also, why do we need different backlog buckets?

See https://wiki.mozilla.org/B2G/Triage#Project_Flags 
(I probably need to promote this idea widely. For now, having the meta bug in parallel is ok).

I think ux-b2g is more for ux blockers and in this case it doesn't look like as one. If it is, someone in UX can add it.
Flags: needinfo?(whuang)
Keywords: feature
Keywords: feature
Priority: -- → P3

Comment 10

8 months ago
Firefox OS is not being worked on
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago8 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.