Closed
Bug 913340
Opened 12 years ago
Closed 12 years ago
Provide mechanism to control which app (and child process) is using NFC
Categories
(Firefox OS Graveyard :: NFC, defect)
Tracking
(blocking-b2g:1.3+, firefox28 fixed)
| Tracking | Status | |
|---|---|---|
| firefox28 | --- | fixed |
People
(Reporter: pauljt, Assigned: dgarnerlee)
References
Details
(Whiteboard: [FT:RIL])
Web NFC currently has a concept of sessions, but the session id broadcast to all child processes. As such apps with NFC permission can probably interfere with other apps that might be using it. This is a known issue, I am just raising this to track its resolution.
| Reporter | ||
Updated•12 years ago
|
Group: b2g-core-security
Updated•12 years ago
|
blocking-b2g: --- → 1.3+
Updated•12 years ago
|
Whiteboard: [FT:RIL]
| Assignee | ||
Comment 1•12 years ago
|
||
I'm looking for a place to upload a patch for system/js/nfc_manager.js Gaia code. This a good place?
Or an existing "catch-all" bug, where it currently is: Bug 860910
-Garner
Comment 2•12 years ago
|
||
(In reply to Garner Lee from comment #1)
> I'm looking for a place to upload a patch for system/js/nfc_manager.js Gaia
> code. This a good place?
>
> Or an existing "catch-all" bug, where it currently is: Bug 860910
>
> -Garner
We can discuss this in next Monday meeting. The nfc manage may be a little different from current design.
Comment 3•12 years ago
|
||
Ken, is there any update that we can share / post here from your meeting? Thanks!
And, who could be the best owner for this bug?
Flags: needinfo?(kchang)
Comment 4•12 years ago
|
||
Garner is the right owner.
Assignee: nobody → dgarnerlee
Flags: needinfo?(kchang)
Comment 5•12 years ago
|
||
It seems better to finish this bug before sprint5. If you think it isn't reasonable, please update target milestone.
Updated•12 years ago
|
Target Milestone: --- → 1.3 Sprint 5 - 11/22
| Assignee | ||
Comment 6•12 years ago
|
||
The current landed DOM provides this functionality, via [ChromeOnly] setSessionToken(token) calls in MozNFCPeer and MozNFCTag. The app passes the same token to GetNFCPeer or GetNFCTag received from the Activity, and the call will register and associate that token with the app until it is invalid (NFC Tag presense is lost).
Close?
Flags: needinfo?(ptheriault)
| Reporter | ||
Comment 7•12 years ago
|
||
Sounds good to me - the point of this bug was to make it so one app at time can use NFC, and from our email discussion sounds like this is the case so nothing more to be done here I think.
I'll look at this code a bit deeper next week when I revisit the NFC review but this can be closed now I think.
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(ptheriault)
Resolution: --- → FIXED
Updated•12 years ago
|
status-firefox28:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•