WebAPI/WebNFC: Difference between revisions

No edit summary
Line 2: Line 2:


* Technologies:
* Technologies:
** Focus on NDEF standard only for now.
** Focus on NDEF standard only for now
** Others (e.g. proprietary MIFARE) to be investigated later.
** Others (e.g. proprietary MIFARE) to be investigated later.
* Capabilities:
* Capabilities:
** read-only for now.
** Read-only for now
** Tag creation/simulation and two-way communication to be investigated later.
** Tag creation/simulation and two-way communication to be investigated later
* Implementation:
* Implementation:
** NDEF-only API available on navigator.mozNfc.ndef object.
** NDEF-only API available on navigator.mozNfc.ndef object
** Discovered NDEF tags are automatically parsed and dispatched to content in the "tagdiscovered" event on navigator.mozNfc.ndef.
** Discovered NDEF tags are automatically parsed and dispatched to content in the "tagdiscovered" event on navigator.mozNfc.ndef
** navigator.mozNfc only available to a specific privileged content page (cf. WebTelephony, WebSMS).
** navigator.mozNfc only available to a specific privileged content page (cf. WebTelephony, WebSMS).
** For now, content is expected to do filtering and dispatching to handlers e.g. via WebIntents/WebActions.
** For now, content is expected to do filtering and dispatching to handlers e.g. via WebIntents/WebActions


== Proposed API ==
== Proposed API ==
canmove, Confirmed users
725

edits