Closed Bug 1007569 Opened 10 years ago Closed 10 years ago

[NFC] Connect to BT-earphone dialog is different from UX spec and after pressed "paired confirm", screen will hang.

Categories

(Firefox OS Graveyard :: NFC, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.0 verified)

VERIFIED FIXED
2.0 S2 (23may)
Tracking Status
b2g-v2.0 --- verified

People

(Reporter: ashiue, Assigned: kamituel)

References

Details

Attachments

(9 files)

Gaia      347d0517f0a77122c876d5f62c0942006a7a0bfe
Gecko     https://hg.mozilla.org/mozilla-central/rev/8be0e21fd300
BuildID   20140507160203
Version   32.0a1

A phone with NFC, and a NFC-capable bluetooth earphone

STR:
1. Enable NFC in settings
2. Tap the phone with bluetooth earphone
3. After NFC detected, click paired confirm

Expected result:
Connect NFC earphone successfully without any problem

Actual result:
Screen hang on unless click home button
We need Arno's help.
Assignee: nobody → arno
Summary: [NFC] After pressed "paired confirm" with NFC-capable bluetooth earphone, currently screen will hang on → [NFC] After pressed "paired confirm" with NFC-capable bluetooth earphone, currently screen will hang
Attached image dialog when BT is off
Attached image dialog when BT is on
The confirm dialog(both BT on and off) is different from UX design. Please refer page 6 and 7.
There are two issues in this bug
1. The UX is different from spec, as Alison mentioned in Comment 2 ~ Comment 4.
2. After the confirmation dialog, the screen will hang, but we can still drag the notification bar and press Home key, as Alison mentioned in Comment 0.

Right now only this dialog will have the 'hang' problem, so we suspect that the 'Pairing Dialog' has some bugs in the event handling and UI.
Summary: [NFC] After pressed "paired confirm" with NFC-capable bluetooth earphone, currently screen will hang → [NFC] Connect to BT-earphone dialog is different from UX spec and after pressed "paired confirm", screen will hang.
Hi!
Regarding those two issues:
1. UX: I've fixed it - I believe it matches the spec now. Allison, could you review it? I'll post screenshots in a sec.
2. Screen hang: issue was that SystemDialog.hide() was overriden and thus, not called. This meant "system-dialog-hide" event was never dispatched and SystemDialogManager never removed "dialog" class from div#screen.

Here's my current work: https://github.com/kamituel/gaia/commit/b899f7ebe495eac5c4ca78b478a12c426e7ebe1e.
Once UX gets r+, I'll mark code for review as well.
Flags: needinfo?(ashiue)
Attached image bt-off-name-known
Attached image bt-on-name-unknown
Attached image bt-on-name-known
Attached image bt-on-name-unknown
Comment on attachment 8420541 [details]
bt-on-name-unknown

Marking you, @ashiue, r? for one of the attachments.
Attachment #8420541 - Flags: review?(ashiue)
Comment on attachment 8420541 [details]
bt-on-name-unknown

Please update the wording on buttons. According to UX doc, bt-on wording should be "No" and "Yes". Thank you!
Attachment #8420541 - Flags: review?(ashiue) → review-
Flags: needinfo?(ashiue)
Hi Kamil,
Could you update the wording on button? 
According to UX doc, bt-off wording should be "Cancel" and "Turn on", and bt-on wording should be "No" and "Yes". 
Except those buttons wording, the dialog looks well! Thank you.
Attached image Fixed button labels.
Hi, thanks for the review :) I've fixed labels. In attachment you'll find two cases, for BT on (left) and off (right) (I've concatenated them to avoid multiple attachments).
Attachment #8420776 - Flags: review?(ashiue)
Attachment #8420776 - Flags: review?(ashiue) → review+
Assignee: arno → kamituel
Status: NEW → ASSIGNED
Attachment #8420879 - Flags: review?(allstars.chh)
Attachment #8420879 - Flags: review?(alive)
Attachment #8420879 - Flags: review?(alive)
Attachment #8420879 - Flags: review+
Attachment #8420879 - Flags: feedback?(l10n)
Comment on attachment 8420879 [details] [review]
Fix for both UI and hang issues.

Alive's r+ is enough.
Attachment #8420879 - Flags: review?(allstars.chh)
Comment on attachment 8420879 [details] [review]
Fix for both UI and hang issues.

The Yes and No are already re-used, and they're re-used in the same context, also visually.

These should be fine to use again.

Side-note, I wish we'd use data-l10n-id changes and mozL10n.translate(), that'd open up a host of hackability for testing and fixing of localizations.
Attachment #8420879 - Flags: feedback?(l10n)
I've fixed L10n remarks:
- "yes"/"no" labels are no re-used.
- I used mozL10n.translate() and mozL10n.localize() instead of .get()
Whiteboard: checkin-needed
Master: https://github.com/mozilla-b2g/gaia/commit/a13d42ab5240008e042d0c61bf9c9d05174e70e4
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: checkin-needed
Target Milestone: --- → 2.0 S2 (23may)
Keywords: verifyme
Verified on
Gaia      101c500903a2477f9de1ea5ce523b9e0be4d45d0
Gecko     https://hg.mozilla.org/mozilla-central/rev/41a54c8add09
BuildID   20140518040203
Version   32.0a1
Status: RESOLVED → VERIFIED
Per comment 21,I clear "verifyme".
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: