Closed Bug 1098443 Opened 5 years ago Closed 2 years ago

Switch back to active call via task manager

Categories

(Firefox OS Graveyard :: Gaia::System::Task Manager, defect)

defect
Not set

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: sfoster, Unassigned)

References

Details

(Keywords: polish, Whiteboard: [systemsfe], ux-tracking)

Currently the call screen for an active call does not appear in the task manager (cards view.) The only way to return to a call if you navigate away from it is to find it in the utility tray. It would be good to make this a real window so it could appear in the task manager and edge gesture (sheets)
See discussion in bug 1096875, from Carrie: 

"I agree on the expected results described in comment 4. I think it's another way to allow users get back to the call. And actually, we did open the dialer APP at that point. So it make sense the page appears in task manager."
blocking-b2g: --- → 2.2?
QA Whiteboard: ux-most-wanted
Blocks: 1098041
Blocks: 994991
Whiteboard: [systemsfe] → [systemsfe], ux-most-wanted-nov2014
Whiteboard: [systemsfe], ux-most-wanted-nov2014 → [systemsfe], ux-most-wanted-nov2014, 2x-uxnom
blocking-b2g: 2.2? → backlog
Keywords: polish
blocking-b2g: backlog → ---
Sam do you know if this ever got fixed?
Flags: needinfo?(sfoster)
Whiteboard: [systemsfe], ux-most-wanted-nov2014, 2x-uxnom → [systemsfe], ux-tracking
(In reply to Tiffanie Shakespeare [:tif] UX from comment #2)
> Sam do you know if this ever got fixed?

No we didn't do this. I don't have as strong feelings about it now as we have an animation drawing attention to the utility tray when the call is put in the background. I don't remember how this was before, but I remember it being much more baffling. However, it does seem like you should be able to edge-swipe to get back to it - that how similar spawned-window interactions work elsewhere on the phone.
Flags: needinfo?(sfoster)
Moving to Dialer component, they may have better context on why we implemented it this way?
Component: Gaia::System::Window Mgmt → Gaia::Dialer
Flags: needinfo?(gsvelto)
There's two different things here that caused this behavior. The first one is that the callscreen was part of the dialer but was opened as an attention screen. As with all attention screens it was not visible in the cards view, only accessible via the tray. Launching the callscreen however also launched the dialer which meant that during a call the dialer would be visible in the cards view. Going back to the dialer didn't re-open the callscreen because you can use the dialer during a call, for example for making a second call or for using the extremely-obscure-yet-required-by-certification short string MMI codes (bug 1092161).

That was before bug 990003. After that bug landed the callscreen is not part of the dialer app anymore so it can be launched w/o the dialer app being active (and thus visible in the cards view). We're planning to reverse that in bug 1226195 and we could consider changing the callscreen UX after that. I'm not sure what could be a better design though; maybe changing the dialer so that when a call is ongoing there's an easy way to switch from it to the callscreen?

BTW making the callscreen itself visible in the cards view would require non-trivial work on the window manager; IIRC attention screens are treated quite differently from regular windows.
Flags: needinfo?(gsvelto)
> BTW making the callscreen itself visible in the cards view would require
> non-trivial work on the window manager; IIRC attention screens are treated
> quite differently from regular windows.

So I think this bug is proposing that attention screens should be treated less differently from regular windows - such that they at least show up in StackManager and therefore the task switcher and edge gesture. It would be good to understand what makes attention screens special - apart from the obvious need to be focussed and on top - and if these differences are necessary or legacy. Initial thoughts Etienne?
Flags: needinfo?(etienne)
Moving back to Window Mgmt component, thanks for the input :gsvelto
Component: Gaia::Dialer → Gaia::System::Window Mgmt
(In reply to Sam Foster [:sfoster] from comment #6)
> > BTW making the callscreen itself visible in the cards view would require
> > non-trivial work on the window manager; IIRC attention screens are treated
> > quite differently from regular windows.
> 
> So I think this bug is proposing that attention screens should be treated
> less differently from regular windows - such that they at least show up in
> StackManager and therefore the task switcher and edge gesture. It would be
> good to understand what makes attention screens special - apart from the
> obvious need to be focussed and on top - and if these differences are
> necessary or legacy. Initial thoughts Etienne?

Can we just always show the attentionscreen "toaster" while in cardview (like we do while on the lockscreen)?

Because otherwise there are a _lot_ of ramifications (where in the stack should it be? should we change the transition to reflect this new spatial model? how do we make sense of the toaster with this new transition etc...)
Flags: needinfo?(etienne)
> Can we just always show the attentionscreen "toaster" while in cardview
> (like we do while on the lockscreen)?
> 
> Because otherwise there are a _lot_ of ramifications (where in the stack
> should it be? should we change the transition to reflect this new spatial
> model? how do we make sense of the toaster with this new transition etc...)

I like this idea. What do you think, Francis?
Component: Gaia::System::Window Mgmt → Gaia::System::Task Manager
Flags: needinfo?(fdjabri)
(In reply to Sam Foster [:sfoster] from comment #9)
> > Can we just always show the attentionscreen "toaster" while in cardview
> > (like we do while on the lockscreen)?
> > 
> > Because otherwise there are a _lot_ of ramifications (where in the stack
> > should it be? should we change the transition to reflect this new spatial
> > model? how do we make sense of the toaster with this new transition etc...)
> 
> I like this idea. What do you think, Francis?

Sounds reasonable to me. How about you, Liz?
Flags: needinfo?(fdjabri) → needinfo?(ehunt)
Sounds good to me.
Flags: needinfo?(ehunt)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.