Closed
Bug 1057264
Opened 10 years ago
Closed 7 years ago
B2G NFC: Add a [ChromeConstructor] for MozNFCTag
Categories
(Firefox OS Graveyard :: NFC, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: allstars.chh, Unassigned)
References
Details
We need a method which could get the supported Technology(NfcA, NfcB, ... etc) on this tag, to do this we'll also need a [ChromeOnly] constructor to initialize the techList in constructor.
Reporter | ||
Updated•10 years ago
|
Summary: B2G NFC: Add a [ChromeOnly] Constructor and getSupportedTechnology for MozNFCTag → B2G NFC: Add a [ChromeConstructor] and getSupportedTechnology for MozNFCTag
Comment 1•10 years ago
|
||
Since there's no connect anymore (assuming nfcd simply pre-connects/disconnects on tag lost), what's the proposed API?
[ChromeConstructor(sequence<NFCTechType> typeList)]
interface MozNFCTag {
...
[Throws]
Promise<NFCTag> getSupportedTechnology(NFCTechType type);
NFCTechType getSupportedTechnologyList();
}
Reporter | ||
Comment 2•10 years ago
|
||
ChromeConstructor should be only avaialble to C++ WebIDL bindings.
I will seperate getSupportedTechnology to another bug.
Summary: B2G NFC: Add a [ChromeConstructor] and getSupportedTechnology for MozNFCTag → B2G NFC: Add a [ChromeConstructor] for MozNFCTag
Reporter | ||
Comment 3•10 years ago
|
||
(In reply to Yoshi Huang[:allstars.chh] from comment #2)
> I will seperate getSupportedTechnology to another bug.
Bug 1082303
Reporter | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•