Closed Bug 963010 Opened 11 years ago Closed 11 years ago

[NFC] When shrinking UI showed up, it will be strange when clicked on home button

Categories

(Firefox OS Graveyard :: NFC, defect)

Product:
Firefox OS Graveyard
Component:
NFC
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: wachen, Unassigned)

References

Details

(Whiteboard: [FT:RIL] [mwcdemo2013])

Attachments

(1 file)

Patch
(deleted), text/x-github-pull-request
alive
: review+
Details
most up-to-date pvt build 1/23 for mako STR: 1. launch "settings" app for 2 phones 2. turn on "NFC" for 2 phones 3. launch "browser" for 2 phones 4. press on "home button" for one of the phone expected result: NFC disconnected and it went back to homescreen actual result: NFC pairing is not disconnected, and it went back to homescreen with black shrinking UI on the background
STR: 1. launch "settings" app for 2 phones 2. turn on "NFC" for 2 phones 3. launch "browser" for 2 phones 4. tap the phone together 5. press on "home button" for one of the phone
If the expected result is per UX defined, we should nominate it as 1.4?
blocking-b2g: --- → 1.4?
Flags: needinfo?(wachen)
Whiteboard: [FT:RIL]
This is very bad behavior, and there is no UX definition for it.
Flags: needinfo?(wachen)
needinfo UX for input
Flags: needinfo?(jhuang)
I've discussed with Alive before, the home button should be block all the time in this situation. Tapping on home button or long pressing home button should be no function at all when NFC connected. So the correct UX should be: 1. Turn on NFC for both phones 2. Turn on browser 3. Tap the phone together, UI shrink 4. Tap on home button, no function. Keep shrinking browser UI
Flags: needinfo?(jhuang)
Is there any documentation on this discussed behavior? If no, please add it to shrinking UI UX document please.
Flags: needinfo?(jhuang)
Sure! I've updated spec to bug 920882
Flags: needinfo?(jhuang)
Juwei, Thanks for the update! Wesley, Please make this 1.4+ since it is bad behavior that is totally different from UX spec.
Flags: needinfo?(whuang)
Ok to set 1.4+, based on page#10 of the UX doc. https://bug920882.bugzilla.mozilla.org/attachment.cgi?id=8372588
blocking-b2g: 1.4? → 1.4+
Flags: needinfo?(whuang)
Blocks: 894678
Can we find someone to help this bug? Thank you.
Greg, can you please take this bug? It is related to shrinking UI.
Flags: needinfo?(gweng)
Any one who works on this, please do refer to comment 5 for UX design. Also, https://bugzilla.mozilla.org/attachment.cgi?id=811878 UX design is for your reference. If there is any UX issues, please discuss with us. Thanks.
I'll survey how to disable these interruptions during NFC sharing. But I doubt that we may need to do some trick to achieve that.
Flags: needinfo?(gweng)
Whiteboard: [FT:RIL] → [FT:RIL] [mwcdemo2013]
Attached file Patch (deleted) —
Mimic the behavior that LockScreen does to block the home key function during NFC sharing.
Attachment #8379411 - Flags: review?(alive)
No longer going to block - NFC needs to be preffed off in 1.4 per a drivers decision to cut scope to only DSDS & QC required features.
blocking-b2g: 1.4+ → 1.4?
blocking-b2g: 1.4? → ---
sorry, wrong triggered a change :P
blocking-b2g: --- → 1.4?
Comment on attachment 8379411 [details] Patch Strongly recommand to have unit test for state control.
Attachment #8379411 - Flags: review?(alive) → review+
master: https://github.com/mozilla-b2g/gaia/commit/f903eb45eed032a585ec3d4faac7fa38bf958ce8
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
blocking-b2g: 1.4? → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: