Closed
Bug 899926
Opened 11 years ago
Closed 11 years ago
Visual refresh for call duration when call has ended
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect, P2)
Firefox OS Graveyard
Gaia::Dialer
Tracking
(feature-b2g:2.0, tracking-b2g:backlog)
RESOLVED
DUPLICATE
of bug 951606
People
(Reporter: sync-1, Assigned: gtorodelvalle)
References
Details
(Whiteboard: [ucid: comms48, 2.0, FT:COMMS] [priority])
Attachments
(7 files, 20 obsolete files)
AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.171
Firefox os v1.1
Mozilla build ID:20130722070207
DEFECT DESCRIPTION:
When end call,it does not display the length of time be used
REPRODUCING PROCEDURES:
1.dial a call(10010), wait the call connected
2.end the call, it is not display the total duration time of the call --> KO
EXPECTED BEHAVIOUR:
when a connected call ended, it should display the total duration time of the call
ASSOCIATE SPECIFICATION:
TEST PLAN REFERENCE:
USER IMPACT:
Middle
REPRODUCING RATE:
5/5
For FT PR, Please list reference mobile's behavior:
Updated•11 years ago
|
blocking-b2g: --- → koi?
Comment 2•11 years ago
|
||
Hi Carrie, please confirm if this visual proposal it's OK from IxD perspective.
Thanks!
Flags: needinfo?(cawang)
Comment 3•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → gtorodelvalle
Updated•11 years ago
|
Blocks: 1.4-comms-targeted
Assignee | ||
Comment 5•11 years ago
|
||
Hi guys, I have a preliminary working version of the requested functionality but I have doubts regarding the fact that we are not currently including the total call duration in a couple of cases, apart from the one considered in this bug, these are: (1) when ending calls in the group call (see attached screenshot) and (2) when ending calls in call holding scenarios (see attached screenshot). Are these cases considered in any other bug I am not aware of? Should we consider those cases in this very bug? :) Thanks!
Assignee | ||
Comment 6•11 years ago
|
||
Assignee | ||
Comment 7•11 years ago
|
||
Comment 8•11 years ago
|
||
(In reply to gtorodelvalle from comment #5)
> Hi guys, I have a preliminary working version of the requested functionality
> but I have doubts regarding the fact that we are not currently including the
> total call duration in a couple of cases, apart from the one considered in
> this bug, these are: (1) when ending calls in the group call (see attached
> screenshot) and (2) when ending calls in call holding scenarios (see
> attached screenshot). Are these cases considered in any other bug I am not
> aware of? Should we consider those cases in this very bug? :) Thanks!
I think we should consider them as part of this bug, ni to José to provide the visual proposal covering them. Thanks for pointing it out!
Flags: needinfo?(vittone)
Assignee | ||
Comment 9•11 years ago
|
||
On the other hand I have a doubt about a so to call it corner case :-) This is the case when the incoming or outgoing call has not been already established and the screen shows "Incoming" or "Connecting" respectively. If any party hangs up the call, should we show:
"Call Ended
00:00"
Right now this is what I have currently implemented (see the screenshot) but could be adapted to what it may be desired, of course ;-)
Flags: needinfo?(cawang)
Assignee | ||
Comment 10•11 years ago
|
||
Related to comment 8 and although I already commented it to Jose, just wanted to point out that the current implementation of the hanging of calls when other calls are on hold does not reflect the designed visuals (see provided image and screenshot). I do not want what are the plans to implement that screen and if we should consider showing the total duration of the call regarding the current or design cases :-)
Assignee | ||
Comment 11•11 years ago
|
||
Comment 12•11 years ago
|
||
(In reply to gtorodelvalle from comment #9)
> Created attachment 8376124 [details]
> [screenshot] Ending a call before establishing it
>
> On the other hand I have a doubt about a so to call it corner case :-) This
> is the case when the incoming or outgoing call has not been already
> established and the screen shows "Incoming" or "Connecting" respectively. If
> any party hangs up the call, should we show:
> "Call Ended
> 00:00"
> Right now this is what I have currently implemented (see the screenshot) but
> could be adapted to what it may be desired, of course ;-)
Maybe in that case you don't need to show anything as the connection was not even established. so it would be a "null connection" that didn't have any duration.
Assignee | ||
Comment 13•11 years ago
|
||
Comment 14•11 years ago
|
||
(In reply to Jose M. Cantera from comment #12)
> (In reply to gtorodelvalle from comment #9)
> > Created attachment 8376124 [details]
> > [screenshot] Ending a call before establishing it
> >
> > On the other hand I have a doubt about a so to call it corner case :-) This
> > is the case when the incoming or outgoing call has not been already
> > established and the screen shows "Incoming" or "Connecting" respectively. If
> > any party hangs up the call, should we show:
> > "Call Ended
> > 00:00"
> > Right now this is what I have currently implemented (see the screenshot) but
> > could be adapted to what it may be desired, of course ;-)
>
> Maybe in that case you don't need to show anything as the connection was not
> even established. so it would be a "null connection" that didn't have any
> duration.
I agree with you Jose Cantera on this one, but I'd like to know Carrie's thoughts on this. Perhaps you want to know that you spent $0 on that call or it goes without saying.
I'm working on the not covered cases, thanks German for that ;)
Comment 15•11 years ago
|
||
Hi guys,
I think if the call is not established, then we shouldn't add the time duration in this case. If the user is the one hung up the phone, he might be confused and think that he answered it accidentally.
Thanks!
Flags: needinfo?(cawang)
Comment 16•11 years ago
|
||
Flags: needinfo?(vittone)
Comment 17•11 years ago
|
||
Based on the latest dialer visuals this is the proposal to add the call duration when the call is ended.
Attachment #8373295 -
Attachment is obsolete: true
Comment 18•11 years ago
|
||
Attachment #8373296 -
Attachment is obsolete: true
Updated•11 years ago
|
Attachment #8377585 -
Attachment is obsolete: true
Updated•11 years ago
|
Attachment #8377589 -
Attachment description: SPEC.Dialer.incomming_call.png → SPEC.Dialer.Call_Ended_Duration.png
Attachment #8377589 -
Attachment filename: SPEC.Dialer.incomming_call.png → SPEC.Dialer.Call_Ended_Durationpng
Comment 19•11 years ago
|
||
Attachment #8376130 -
Attachment is obsolete: true
Updated•11 years ago
|
Attachment #8377588 -
Attachment description: Call_Ended_Duration.png → [visual] Call_Ended_Duration.png
Comment 20•11 years ago
|
||
Comment 21•11 years ago
|
||
Comment 22•11 years ago
|
||
Comment 23•11 years ago
|
||
Comment 24•11 years ago
|
||
Assignee | ||
Comment 25•11 years ago
|
||
After discussing it with Noemí and Jose and since we found many visual discrepancies between what's currently implemented in master regarding the Dialer and the specifications and visuals provided by UX, we decided to make a proposal of implementation for this bug based on what's currently implemented and not on what should be implemented. The alignment of the current implementation and the Dialer and the specs will be covered in a future bug. In fact, Jose is working on identifying these discrepancies based on the screenshots I have provided him.
Consequently, I am going to attach some screenshots of the solution proposed to this bug, as I said based on the current implementation of the Dialer in master :-)
We will then ask for the OK by Wilfred to make the corresponding pull request and get it landed in master.
Thanks!
Assignee | ||
Updated•11 years ago
|
Attachment #8376105 -
Attachment is obsolete: true
Assignee | ||
Updated•11 years ago
|
Attachment #8376107 -
Attachment is obsolete: true
Assignee | ||
Updated•11 years ago
|
Attachment #8376124 -
Attachment is obsolete: true
Assignee | ||
Updated•11 years ago
|
Attachment #8376131 -
Attachment is obsolete: true
Assignee | ||
Comment 26•11 years ago
|
||
If the call is established, the duration of the call is shown.
Assignee | ||
Comment 27•11 years ago
|
||
If the call is not established, no duration information is shown.
Assignee | ||
Comment 28•11 years ago
|
||
If the call is established, the duration is shown once the call ends.
Assignee | ||
Comment 29•11 years ago
|
||
No duration information is shown if the call is not established.
Assignee | ||
Comment 30•11 years ago
|
||
attachment 8377626 [details] is not currently implemented in master and consequently it has not been adapted in the patch I have prepared. In fact, not really sure what duration UX is planning to provide there (the current ongoing conference duration until the moment the concrete party hung up?). Anyhow, this will be covered in the bug Jose is preparing regarding the discrepancies between the current implementation and the proposed specs so let's not focus on it here ;-)
Assignee | ||
Comment 31•11 years ago
|
||
Although I think this visual has not been attached to this bug, Jose, I have adapted the page when a conference call is finished by the moderator or administrator (so to call it).
In this case, the duration information is always shown since there is no way to reject the establishment of a conference call. It is always established ;-)
Assignee | ||
Comment 32•11 years ago
|
||
attachment 8377627 [details] is not currently implemented in master and consequently it has not been adapted in the patch I have prepared either. BTW, in the current implementation in master, if the ongoing call is "minimized" to the top of the screen (with the green background) and the called party hangs up the call, the (so to call it) green background banner is moved out of the screen by the top. No red background or "Call ended" text is shown.
Comment 33•11 years ago
|
||
ni to Wilfred to confirm the proposal for including call duration info in v1.4 based on what's currently implemented (please see screenshots attached by German).
The visual gap between the current implementation and the specs coming from visual team for dialer will be properly prioritized and addressed (out of the scope of this bug), José is gathering all the discrepancies in a single document that will help on having a clear picture about it. Thanks!
Flags: needinfo?(wmathanaraj)
Comment 34•11 years ago
|
||
call duration is out of v1.4 due to reduced scope and time we have for v1.4. I am backlogging this item and we can perhaps do this as part of the work of visual refresh - but needs evaluation how far away we far with the gap document. if visual refresh captures the gap and addresses it then we have a good chance to do this.
blocking-b2g: --- → backlog
Flags: needinfo?(wmathanaraj)
Updated•11 years ago
|
Blocks: dialer-visual-refres
Comment 35•11 years ago
|
||
Attachment #8377589 -
Attachment is obsolete: true
Comment 36•11 years ago
|
||
Attachment #8377631 -
Attachment is obsolete: true
Comment 37•11 years ago
|
||
Attachment #8377625 -
Attachment is obsolete: true
Comment 38•11 years ago
|
||
Attachment #8377588 -
Attachment is obsolete: true
Comment 39•11 years ago
|
||
I've updated the visuals following the visual refresh.
Comment 40•11 years ago
|
||
Attachment #8382955 -
Attachment is obsolete: true
Comment 41•11 years ago
|
||
Attachment #8382958 -
Attachment is obsolete: true
Updated•11 years ago
|
blocking-b2g: backlog → 1.5?
Updated•11 years ago
|
Blocks: comms_2.0_targeted
Updated•11 years ago
|
No longer blocks: 1.4-comms-targeted
Updated•11 years ago
|
Whiteboard: [priority]
Updated•11 years ago
|
Summary: [Buri][CTA][Call]When end call,it does not display the call duration → Visual refresh for call duration when call has ended
Updated•11 years ago
|
Attachment #8377626 -
Attachment is obsolete: true
Updated•11 years ago
|
Attachment #8383056 -
Attachment is obsolete: true
Updated•11 years ago
|
Attachment #8383055 -
Attachment is obsolete: true
Comment 45•11 years ago
|
||
Hi,
Visual refresh for call duration when call has ended will be handled within Bug 951606 (VR for call screen) and the visual specs will be available in Bug 950760 (VR meta dialer). Thanks!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Updated•11 years ago
|
Attachment #8377629 -
Attachment is obsolete: true
Updated•11 years ago
|
Attachment #8382956 -
Attachment is obsolete: true
Updated•11 years ago
|
Attachment #8382957 -
Attachment is obsolete: true
Updated•11 years ago
|
feature-b2g: --- → 2.0
Updated•10 years ago
|
QA Contact: lolimartinezcr
Updated•10 years ago
|
Whiteboard: [priority] → [ucid: comms48, 2.0, FT:COMMS] [priority]
Updated•10 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•