890451 - [StatusBar] network icon is misleading, when no network.

Status: RESOLVED WONTFIX

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

Description

[Leo]

Attachment: screenshot

When there is no network, the signal bar icon is displayed with zero level.
(Refer to attachment image.)
However, this can be misinterpreted by user as 'connected, but signal is very week.'

In Android, a signal bar with 'X' mark is displayed when there is no network.


In statusbar.js, I could see that the 'X' signal bar is displayed when the following 3 conditions are met.

1) No network
2) 'Network searching' is false.
3) 'Emergency call only' is false.

My question is, shouldn't we remove the 3) condition?

UX team, please confirm.
Thanks


p.s. Would you upload a latest specification/document for the statusbar if you have one.

Comment 1

[Jason Smith [:jsmith]]

UX is probably better group to comment here than me.

Comment 2

[[e-mail]]

Need UX input

Comment 3

[Stephany Wilkes]

Assigning to Casey for systems front-end since this is leo+.

Comment 4

[Casey Yee]

Attachment: Status bar icons

Comment 5

[Casey Yee]

(In reply to Leo from comment #0)
> When there is no network, the signal bar icon is displayed with zero level.
> (Refer to attachment image.)
> However, this can be misinterpreted by user as 'connected, but signal is
> very week.'
> 
> In Android, a signal bar with 'X' mark is displayed when there is no network.

We have the iconography for this and should use the "X" in the no-network cases.


> 
> 
> In statusbar.js, I could see that the 'X' signal bar is displayed when the
> following 3 conditions are met.
> 
> 1) No network
> 2) 'Network searching' is false.
> 3) 'Emergency call only' is false.
> 
> My question is, shouldn't we remove the 3) condition?

I don't see why we should remove condition 3) since in a emergency scenario, you will still want to see the signal indicator even if you can't make a regular call.

We do have status bar specs but they are slightly out of date and preclude the "X" graphic for no signal.

Comment 6

[Casey Yee]

Attachment: (Out of date) Status bar spec.

Comment 7

[Mark Shiao]

Hi Casey,

I'm on the fence about this one. The iconography indicates a network connection, however in this case there's not a valid network connection.  Nonetheless, I can see the argument of having some type of indicator to communicate that an emergency call is available. How do the other OSs handle this?  Just my two cents here.   

If we are not planning to change the behavior as stated in the bug report than please confirm this and I will close this ticket. 

Thanks,
Mark

Comment 8

[Leo]

(In reply to Mark Shiao from comment #7)

We'll accept what you guys decide. We are fine as long as operators are ok with it.
Removing leo flag.
Thanks.

Comment 9

[Mark Shiao]

Hi Casey,

Can you confirm that no changes will be made so that I can close this bug.

Thanks,
Mark

Comment 10

[Casey Yee]

(In reply to Mark Shiao from comment #7)
> Hi Casey,
> 
> I'm on the fence about this one. The iconography indicates a network
> connection, however in this case there's not a valid network connection. 
> Nonetheless, I can see the argument of having some type of indicator to
> communicate that an emergency call is available. How do the other OSs handle
> this?  Just my two cents here.   

But the connection and signal _is_ valid.   The user just isn't allowed to make anything except emergency calls.    I think it's important to show the signal strength as long as there is one.   I can see this being useful in a survival situation.

We could create a separate icon for emergency calls only but I think it would be difficult to make a icon clear enough to communicate that.    Plus we already have enough messaging in various places to indicate that only emergency calls can be made.

Also, it seems that both android and ios show the signal indicator when in emergency call only cases.


> 
> If we are not planning to change the behavior as stated in the bug report
> than please confirm this and I will close this ticket. 
> 

I don't believe anything needs to be changed.  This behavior seems normal and what should be expected.

> Thanks,
> Mark