Closed Bug 1048717 Opened 10 years ago Closed 10 years ago

[Messages][Refresh] Display call button at the header of single recipient thread

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(feature-b2g:2.2+, tracking-b2g:backlog)

RESOLVED FIXED
2.1 S4 (12sep)
feature-b2g 2.2+
tracking-b2g backlog

People

(Reporter: azasypkin, Assigned: azasypkin)

References

Details

(Whiteboard: [p=1])

Attachments

(3 files)

No description provided.
Hey Jenny, Just two quick questions regarding to the latest page in this spec: * If we move "Call" button to the header, should it still be duplicated in the contact menu (when tapping on recipient name)? * If not, we'll have single option in the contact menu ("View contact"), so should we keep single-item-menu or tap on header should lead to "View contact" directly without displaying menu?
Flags: needinfo?(jelee)
(In reply to Oleg Zasypkin [:azasypkin] from comment #1) > Hey Jenny, > > Just two quick questions regarding to the latest page in this spec: > > * If we move "Call" button to the header, should it still be duplicated in > the contact menu (when tapping on recipient name)? > > * If not, we'll have single option in the contact menu ("View contact"), so > should we keep single-item-menu or tap on header should lead to "View > contact" directly without displaying menu? In the past I asked for having a single item menu here, in the same situation (the action was "call"). The menu acts as a "confirmation" menu, to prevent unwanted taps. But see also bug 1040874. If there is only this menu left, I think we'll just remove this menu in the end.
See also bug 1032273, it's related to this button.
Hi Wesley, Since this feature is separated from bug 1026694, could you please set flag (feature-b2g: 2.1) for this bug?
Flags: needinfo?(whuang)
QA Whiteboard: [COM=Gaia::SMS]
It's part of the visual refresh.
feature-b2g: --- → 2.1
Flags: needinfo?(whuang)
(In reply to Oleg Zasypkin [:azasypkin] from comment #1) Hello Oleg, see my comments below: > * If we move "Call" button to the header, should it still be duplicated in > the contact menu (when tapping on recipient name)? > Nope, let's remove it from contact menu. > * If not, we'll have single option in the contact menu ("View contact"), so > should we keep single-item-menu or tap on header should lead to "View > contact" directly without displaying menu? I think we should keep the menu for consistency, as in other cases, there can be more than one option. I don't think it's reasonable to go to view contact directly when this is the only available option, because the contact name itself doesn't imply the "view contact" function. So let's keep the on option menu for now. Tks :)
Flags: needinfo?(jelee)
(In reply to Jenny Lee from comment #6) > (In reply to Oleg Zasypkin [:azasypkin] from comment #1) > > Hello Oleg, see my comments below: > > > * If we move "Call" button to the header, should it still be duplicated in > > the contact menu (when tapping on recipient name)? > > > Nope, let's remove it from contact menu. > > > * If not, we'll have single option in the contact menu ("View contact"), so > > should we keep single-item-menu or tap on header should lead to "View > > contact" directly without displaying menu? > > I think we should keep the menu for consistency, as in other cases, there > can be more than one option. I don't think it's reasonable to go to view > contact directly when this is the only available option, because the contact > name itself doesn't imply the "view contact" function. So let's keep the on > option menu for now. Tks :) Thanks for clarification!
Per product prioritization, this could be 2.2 focus.
blocking-b2g: --- → backlog
feature-b2g: 2.1 → 2.2
Use feature-b2g:2.2? rather than just 2.2.
feature-b2g: 2.2 → 2.2?
No longer blocks: sms-refresh-v2.1
Assignee: nobody → azasypkin
Blocks: 1061491
Whiteboard: [p=1
Target Milestone: --- → 2.1 S4 (12sep)
Whiteboard: [p=1 → [p=1]
Status: NEW → ASSIGNED
Attached file GitHub pull request URL (deleted) —
Hey Steve, Could you please review this patch? Thanks!
Attachment #8483996 - Flags: review?(schung)
Comment on attachment 8483996 [details] GitHub pull request URL R=me, only some nits in test, thanks!
Attachment #8483996 - Flags: review?(schung) → review+
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
let's keep the already-landed improvement in 2.2.
feature-b2g: 2.2? → 2.2+
Flags: in-moztrap?(echang)
Added a test case
Flags: in-moztrap?(echang) → in-moztrap-
Flags: in-moztrap- → in-moztrap+
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: