883750 - [Dialer][Contacts] Tapping on any call log entry opens the visual underlying entry from contacts but not for this contact

Status: RESOLVED DUPLICATE of bug 883756

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

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/537f3eac4c48
Gaia   0c836be7f24693b74ad7fd21c8153824f1c7f548
BuildID 20130613230207
Version 18.0

At the moment our dialer does not correctly handle a phone number which is in use by multiple contacts. Once you do a call to such a number via the contacts app, you will get a log entry like 'Foo Bar or X other'. When you want to redial that number and click on that log entry, the contacts application will open but does not present a list of possible contacts. Instead the information page for the contact which visually is located at the same area you tapped on will be opened. We should better do a search and display the list of possible contacts.

At the moment you cannot easily re-dial, and that not only because of bug 840655 but also that you have to do again a search for the contact.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

So this happens not only for contacts which have a phone number used multiple times across different contacts. I was able to also see it with a contact which has its own numbers. So clicking on its entry in the call log opened the details for a contact in the contact list located behind it.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

I cannot longer test this because bug 883770 blocks me here, given that I even don't see any contact name at all at the moment.

Comment 3

[Julien Wajsberg [:julienw]]

Etienne, do you think this is rather a bug in Contacts (for Henrik: the Contacts app is what's effectively displayed in the dialer), or are we doing something wrong in Dialer ?

Comment 4

[Germán Toro del Valle (:gtorodelvalle)]

The issue pointed out in comment 2 of this bug is being solved in bug 883756.

Comment 5

[Germán Toro del Valle (:gtorodelvalle)]

Definitely this bug should focus on the distinct contacts with the same phone number assigned which is not solved by the patch provided for bug 883756.

I think it would be great if you could settle on the test case which you are testing and which fails, Henrik, probably via a concrete set of steps to reproduce it. Just my 2 cents... ;-)

Comment 6

[Mike Lee [:mlee]]

Henrik,

Please clarify the relationship between bug 883770, bug 883756, bug 840655 and this bug 883750.

Our current understanding is that:

* bug 840655: Call Log: Can't dial an entry; ux design decision being discussed.
* bug 883750: Call Log: Tapping shows wrong contact's details; unrelated phone #s.
* bug 883756: Call Log: Tapping shows wrong contact's details; shared phone #s.
* bug 883770: Call Log: No contacts displayed; only phone numbers.

So:
 
* Should bug 883770 block bug 840655, bug 883750, and bug 883756?
* Are bug 883750 and bug 883756 two symptoms of the same underlying problem?

Thanks,
Triage

Comment 7

[Alex Keybl [:akeybl]]

This doesn't appear to be a regression or a blocker for partners.

Comment 8

[Henrik Skupin [:whimboo][⌚️UTC+1]]

I what I see here is clearly the same symptom as bug 883756, which has been filed later but has a PR attached. So I'm going ahead and dupe my bug to bug 883756.