Closed Bug 1057264 Opened 7 years ago Closed 4 years ago

B2G NFC: Add a [ChromeConstructor] for MozNFCTag

Categories

(Firefox OS Graveyard :: NFC, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

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.
Summary: B2G NFC: Add a [ChromeOnly] Constructor and getSupportedTechnology for MozNFCTag → B2G NFC: Add a [ChromeConstructor] and getSupportedTechnology for MozNFCTag
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();
}
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
(In reply to Yoshi Huang[:allstars.chh] from comment #2)
> I will seperate getSupportedTechnology to another bug.
Bug 1082303
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.