Closed
Bug 1000678
Opened 11 years ago
Closed 11 years ago
Don't initiate NFC sharing when on the browser start page
Categories
(Firefox OS Graveyard :: Gaia::Browser, defect)
Tracking
(feature-b2g:2.0, tracking-b2g:backlog, b2g-v2.0 affected, b2g-v2.1 unaffected, b2g-v2.2 unaffected, b2g-master unaffected)
VERIFIED
FIXED
2.0 S2 (23may)
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | affected |
b2g-v2.1 | --- | unaffected |
b2g-v2.2 | --- | unaffected |
b2g-master | --- | unaffected |
People
(Reporter: ashiue, Assigned: benfrancis)
References
Details
(Whiteboard: [systemsfe][p=3])
Attachments
(4 files)
Gaia 0a4d2dea25a7162ee43db3a0db817798b70e7521
Gecko https://hg.mozilla.org/mozilla-central/rev/1ab07aa4d004
BuildID 20140422160202
Version 31.0a1
STR:
1. launch "settings" app for 2 phones
2. turn on "NFC" for 2 phones
3. launch "browser" from phone A (on browser Homepage page)
4. tap 2 phones
Expected result:
Browser Homepage page should not show shrinking UI because it could not be shared
Actual result:
Browser Homepage page show shrinking UI
Reporter | ||
Updated•11 years ago
|
Summary: [NFC] Browser default page would still show shrinking UI when nfc device detected → [NFC] Browser homepage page would still show shrinking UI when nfc device detected
Blocks: NFC-Gaia
Comment 1•11 years ago
|
||
Hi Candice,
I guess the mechanism should be on browser app, to determine whether it is a sharable content or not.
blocking-b2g: --- → backlog
Flags: needinfo?(cserran)
Whiteboard: [systemsfe]
Comment 2•11 years ago
|
||
Hey Wesley,
Ben will be taking a look at this in this sprint as we reviewed in sprint planning today and will be tracking
Assignee: nobody → bfrancis
Flags: needinfo?(cserran)
Target Milestone: --- → 2.0 S1 (9may)
Updated•11 years ago
|
blocking-b2g: backlog → 2.0+
Comment 4•11 years ago
|
||
(In reply to Wesley Huang [:wesley_huang] from comment #1)
> Hi Candice,
>
> I guess the mechanism should be on browser app, to determine whether it is a
> sharable content or not.
Yes, the NFC onpeerready callback that's being inspected should not be set if the app determines can't be shared in the current context.
Assignee | ||
Updated•11 years ago
|
Target Milestone: 2.0 S1 (9may) → 2.0 S2 (23may)
Assignee | ||
Updated•11 years ago
|
Component: NFC → Gaia::Browser
Summary: [NFC] Browser homepage page would still show shrinking UI when nfc device detected → Don't initiate NFC sharing when on the browser start page
Whiteboard: [systemsfe] → [systemsfe][p=3]
Updated•11 years ago
|
blocking-b2g: 2.0+ → backlog
feature-b2g: --- → 2.0
Assignee | ||
Comment 5•11 years ago
|
||
Attachment #8425654 -
Flags: review?(dale)
Comment 6•11 years ago
|
||
Comment on attachment 8425654 [details] [review]
https://github.com/mozilla-b2g/gaia/pull/19450
looks good, cheers
https://github.com/mozilla-b2g/gaia/commit/3c823798b638e637c6c1985d266b9510c58db553
Attachment #8425654 -
Flags: review?(dale) → review+
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•11 years ago
|
||
Verified on
Gaia 7db23414f2d632f4d00b5023ac1090b6045dc5fd
Gecko https://hg.mozilla.org/mozilla-central/rev/2619a4def1b9
BuildID 20140522160203
Version 32.0a1
Status: RESOLVED → VERIFIED
Comment 9•10 years ago
|
||
Hi Reporter,
I can repro this bug on latest Flame v2.0. Could you help with checking it again?
Thank you.
Repro STR:
1. Launch "Settings" app and turn on "NFC" for 2 phones.
2. Launch "Browser" on Flame v2.0(stay Browser Homepage page)
3. Tap 2 phones together.
**Browser Homepage page show shrinking UI. --KO
Flame v2.0 build:
Gaia-Rev 2989f2b2bd12fcc0e9c017d2db766e76a55873b8
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/b4c61fd1dcfc
Build-ID 20150126000204
Version 32.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20150126.033406
FW-Date Mon Jan 26 03:34:17 EST 2015
Bootloader L1TC000118D0
Flags: needinfo?(ashiue)
Updated•10 years ago
|
Comment 10•10 years ago
|
||
Comment 11•10 years ago
|
||
Add video and log.
Updated•10 years ago
|
QA Whiteboard: [MGSEI-Triage+]
Comment 13•10 years ago
|
||
According to https://bugzilla.mozilla.org/show_bug.cgi?id=1138508#c15, this problem have fixed on flame 3.0, set the Tracking Flag of Flame 3.0 to unaffected.
status-b2g-master:
--- → unaffected
Updated•10 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•