Closed Bug 1032282 Opened 11 years ago Closed 11 years ago

[Flatfish] [Lockscreen] Hide emergency call button

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joshua-s, Assigned: chens)

References

Details

(Keywords: verifyme, Whiteboard: [Flatfish][TCP])

Attachments

(2 files)

Since the flatfish device does not have cellular capabilities, it is pointless and confusing to have an Emergency Call button on the lockscreen.
This is actually a UX improvement...
Blocks: flatfish-ux
No longer blocks: flatfish
Which is build is this on? Is this on a bug for regular phones?
This is a problem in all the builds I have tested. To clarify the location of the button: it is on the passcode entry keyboard. This is not an issue on phones because they have a cellular connection.
Okay, I can reproduce.
OS: Other → Gonk (Firefox OS)
Hardware: Other → ARM
Whiteboard: [Flatfish] → [Flatfish][TCP]
I think testing for |if(navigator.mozTelephony)| should be enough. I haven't worked on the tablet though so I hope this API is not available. If it is available, we probably want to file a bug to remove it on systems that can't place a phone call.
Depends on: 1034196
Assigning to me!
Assignee: nobody → thewanuki
I think this issue is fixed in latest master?
Status: NEW → UNCONFIRMED
Ever confirmed: false
Putting verifyme keyword in to check to see if this is resolved in latest.
Keywords: verifyme
See Also: → 928643
Attached image Lockscreen screenshot
Screenshot on tablet w/ latest gaia Gaia cab9e0dd0dee93f31f12313d012e660f074663cf Gecko 51ac93f62dfaba70de71610bbc14e0b62d7e0525 BuildID 20140714014330 Version 33.0a1
Thank you Sherman! This issue is actually shown on the pass-code entry field. To enable this, please go to Settings > Privacy and Security > Screen lock and enable Passcode lock.
Attached file Pull request
Attachment #8465257 - Flags: review?(gweng)
Comment on attachment 8465257 [details] [review] Pull request OK, but please wait for the CI result.
Attachment #8465257 - Flags: review?(gweng) → review+
Comment on attachment 8465257 [details] [review] Pull request This is missing a new test.
Attachment #8465257 - Flags: review+ → review-
While I indeed miss that check (my fault), my concern is to change another one's review directly is proper or not. What I've experienced is to set f-, not overwrite the existing one.
Comment on attachment 8465257 [details] [review] Pull request To restore the flag as it could be. Maybe I'm wrong, but what I've experienced and heard is we should not change another one's review flag directly. It should come with a f- .
Attachment #8465257 - Flags: review-
Comment on attachment 8465257 [details] [review] Pull request PR update and tests added
Attachment #8465257 - Flags: review?(gweng)
Assignee: thewanuki → shchen
Comment on attachment 8465257 [details] [review] Pull request Review+ with nits. Please fix them and make sure CI result is green.
Attachment #8465257 - Flags: review?(gweng) → review+
Thanks for the comment, PR updated.
Attachment #8465257 - Flags: feedback?(gweng)
Comment on attachment 8465257 [details] [review] Pull request While I set r+ with nits means you can land the code after you fix the nits. If you still want to set review to confirm that, you can set review again.
Attachment #8465257 - Flags: feedback?(gweng)
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: