Closed Bug 928700 Opened 11 years ago Closed 10 years ago

[wasabi] CDMA call waiting improvement

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: echu, Unassigned)

References

Details

Attachments

(3 files)

+++ This bug was initially created as a clone of Bug #915081 +++

[Version Info]
Gaia:     2d870100a945272824f8e42a8c52aac095fe907e
  B-D     2013-09-11 04:59:20
Gecko:    46c335b301fdb32f47e58c665190ffc41522ae00
BuildID   20130911062051
Version   26.0a1

* Symptom:
The 2nd incoming call screen needs to be improved to latest UX spec.

* Reproduce Steps
1. Make a call to other device or MT call to DUT.
2. MT a second call to DUT.

* Actual results:
1. The 2nd incoming call screen UI is not follow UX spec.

* Expected results:
1. It should follow spec's UI defintion.
blocking-b2g: --- → koi?
Instead of nomming this for koi right away which might be a bit risky I would suggest to do the following: I'll try to work on this as soon as I've cleared my koi+ backlog; once I get the patch ready (that might be fairly large) we can do a risk assessment based on the real code and then nom for koi+ or not depending on the outcome.
(In reply to Gabriele Svelto [:gsvelto] from comment #1)
> Instead of nomming this for koi right away which might be a bit risky I
> would suggest to do the following: I'll try to work on this as soon as I've
> cleared my koi+ backlog; once I get the patch ready (that might be fairly
> large) we can do a risk assessment based on the real code and then nom for
> koi+ or not depending on the outcome.

I will discuss with EPM/EM in Triage meeting this week and will update the flag accordingly. Thank you.
since there's no function wise problem + according to triage result, changed to 1.3+ with target milestone on 12/6
blocking-b2g: koi? → 1.3+
Target Milestone: --- → 1.3 Sprint 6 - 12/6
These images are from Jacqueline. As we discussed in past mail, Jacqueline will provide specs for implementation, right?
Flags: needinfo?(jsavory)
this is a redesign on call waiting. 1.4?
blocking-b2g: 1.3+ → 1.4?
Flags: needinfo?(cawang)
Flags: needinfo?(cawang) → needinfo?(jhuang)
Hi all, I've clarified the final spec from Mike:

1) For CDMA, an incoming call pops out with two options: Answer and hold current/ Ignore call
2) For GSM, an incoming call page pops out with three options: Answer and hold current/ Answer and end current/ Ignore call

The ux spec should be finished by 1.3, but since I am the owner of CDMA 1.4 now, I'll help to update ux spec by next week.
Flags: needinfo?(jsavory)
Flags: needinfo?(jhuang)
Hi all, ux spec updated.
Wilfred, shall we take it for 1.4 ?
Flags: needinfo?(wmathanaraj)
we can work on it as time permits and if it passes review we can land - but not block v1.4 on this item.
Flags: needinfo?(wmathanaraj)
Wayne, is this needed for Madai?
blocking-b2g: 1.4? → madai?
Flags: needinfo?(wchang)
Target Milestone: 1.3 Sprint 6 - 12/6 → ---
(In reply to Joe Cheng [:jcheng] from comment #10)
> Wayne, is this needed for Madai?

Not as long as it doesn't break existing/other functionality.
Flags: needinfo?(wchang)
No longer blocks: 970187
blocking-b2g: madai? → ---
Whiteboard: [FT:RIL]
This bug is out of date and we suspect that it's no longer valid. If you think this is in error, please reopen it.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: