Closed Bug 920422 Opened 11 years ago Closed 11 years ago

[Dialer] The flow is not correct when a call is ongoing and user tries to add another participant

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:koi+, b2g-v1.2 fixed)

VERIFIED FIXED
blocking-b2g koi+
Tracking Status
b2g-v1.2 --- fixed

People

(Reporter: isabelrios, Assigned: etienne)

Details

(Whiteboard: [u=commsapps-user c=dialer p=0])

Attachments

(4 files)

Attached image 2013-09-25-09-54-10.png
09/24 v1.2 build:
Gecko-85ead36
Gaia-a22ba4a

STR
1. Open dialer and make a call
2. Once the call is stablished, tap on the '+' icon to add a participant

EXPECTED
The screen is shown fine.
Copying Victoria who could help to show the correct screen to be shown.

ACTUAL
Please see screenshot attached.
Again, needinfoing Victoria to get actionable input.
Flags: needinfo?(vpg)
This is not a visual issue, it is a flow one. Please refer to the specs (https://mozilla.app.box.com/s/cpwxyeisjurklut93f0a) as when you tap on the "add participant" button it should take you to the contacts list and not the call log, so you can pick a contact or I guess use dialer to dial the number if it's not in your already saved contacts.

I have opened a new bug to follow up the layout implementation polishing for this component: https://bugzilla.mozilla.org/show_bug.cgi?id=921056

Thanks!
Flags: needinfo?(vpg)
More info, the call log is open because it has been previously used. 
If dialer has not been open before nor the call log, the app is not in background then, when tapping on '+' when there is call ongoing, the dialer is shown. But it is shown with the first number dialed and with the status bar shown wrongly, please see screenshot attached.
Attached image 2013-09-27-09-34-29.png
triage: koi+ for UI problems
maybe a dup of Bug 920298 and bug 918534
blocking-b2g: koi? → koi+
Changing the subject to clarify the issue to cover here.
The flow is not correct when adding a participant to a call. There are several scenarios which does not follow the specs https://mozilla.app.box.com/s/cpwxyeisjurklut93f0a, page 15.

Dialer is closed: when tapping on '+' when there is call ongoing, the dialer is shown. But it is shown with the first number dialed and with the status bar shown wrongly, please see screenshot attached.

Dialer has been open and is in background: when tapping on '+' the dialer is open in the state is had been open las time, it means, if call log was open, the it will be shown (attachment 2013 [details]-09-25-09-54-10.png).

When tapping on '+' what should be open is the contact list.
Summary: [Dialer] Screen is not shown correctly when a call is ongoing and user tries to add another participant → [Dialer] The flow is correct when a call is ongoing and user tries to add another participant
Summary: [Dialer] The flow is correct when a call is ongoing and user tries to add another participant → [Dialer] The flow is not correct when a call is ongoing and user tries to add another participant
Thanks Isabel, crystal clear!
Assignee: nobody → etienne
Attached file Pointer to gaia PR
I tried really hard but couldn't find a way to test:
* posting messages on window.opener
* window.location.hash changes

And I don't want to make structural changes to these files to make them more testable in a koi+ patch.
Attachment #813234 - Flags: review?(anthony)
Comment on attachment 813234 [details]
Pointer to gaia PR

Yabon.
Attachment #813234 - Flags: review?(anthony) → review+
https://github.com/mozilla-b2g/gaia/commit/47f50a6822bf2cd8635bc215e2fb09642d8eaf5c
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Uplifted 47f50a6822bf2cd8635bc215e2fb09642d8eaf5c to:
v1.2: 4e46fe4312fd8c6686f811020e0b1cd4e14a4b46
I re-checked this bug and now the flow is as described.
User is taken to contacts list: 
According to the wfs: https://mozilla.app.box.com/s/cpwxyeisjurklut93f0a/1/1030018334/9944055924/1, pag 15/42. 

But, when there are no contact(s), should be shown the empty contact list screen?
I am attaching here the current view when there are not contact(s) in the address book. 
Cc and ni Ayman
Attached image Empty contact list.png
Flags: needinfo?(aymanmaat)
(In reply to Isabel Rios [:isabel_rios] from comment #12)
> I re-checked this bug and now the flow is as described.
> User is taken to contacts list: 
> According to the wfs:
> https://mozilla.app.box.com/s/cpwxyeisjurklut93f0a/1/1030018334/9944055924/1,
> pag 15/42. 
> 
> But, when there are no contact(s), should be shown the empty contact list
> screen?
> I am attaching here the current view when there are not contact(s) in the
> address book. 
> Cc and ni Ayman

I would suggest that if there are no contacts in the contact list that we take the user straight to the Dialler as it is pointless showing them an empty contact list in this instance.

ni? to Jacqueline who is underwriting the UX specs for Dialler to confirm this or to make a counter proposal.
Flags: needinfo?(aymanmaat) → needinfo?(jsavory)
(In reply to ayman maat :maat from comment #14)
> I would suggest that if there are no contacts in the contact list that we
> take the user straight to the Dialler as it is pointless showing them an
> empty contact list in this instance.

Makes sense to me, but this should probably be a follow-up non blocking bug because it won't be straightforward.
(In reply to Etienne Segonzac (:etienne) from comment #15)
> (In reply to ayman maat :maat from comment #14)
> > I would suggest that if there are no contacts in the contact list that we
> > take the user straight to the Dialler as it is pointless showing them an
> > empty contact list in this instance.
> 
> Makes sense to me, but this should probably be a follow-up non blocking bug
> because it won't be straightforward.

Hi,

A follow up bug has been created for covering "no contacts" scenario - bug 926825
I agree with Ayman's proposal for the no contacts case, as it is essentially one less step for the user.
Flags: needinfo?(jsavory)
Checked this bug but did not verify it before, changing the status now after testing with v1.2 11/29 build:
Gecko-e537f6f
Gaia-075e60c
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: