public-web-nfc@w3.org from November 2015 by subject

[web-nfc] add a cancelAll() instead of cancelPush()

[web-nfc] Add method for clearing all watches?

[web-nfc] Add more examples and improve existing ones

[web-nfc] Avoid resemblance with postMessage

[web-nfc] cancelPush should return Promise<void>

[web-nfc] Change object to Dictionary. Modify receive steps to parse JSON content.

[web-nfc] Change type of timeout to unrestricted double fix #81

[web-nfc] Clamp NFCPushOptions.timeout and provide default values

[web-nfc] Consider removing .nfc namespace

[web-nfc] Define the same NFCMessage both for push and read

[web-nfc] Fix #65. Improve requestAdapter() steps based on #67 discussion.

[web-nfc] Fix examples: remove JSON.stringify and parse. Fix the receive steps.

[web-nfc] Fix TAG review comments.

[web-nfc] Handle case when NFC support is disabled

[web-nfc] Make NFCPushOptions optional for pushMessage

[web-nfc] More flexible parameter to push()

[web-nfc] new commits pushed by anssiko

[web-nfc] new commits pushed by kenchris

[web-nfc] new commits pushed by zolkis

[web-nfc] Potentially abstracting the payload contents a bit more from the NDEF records and from the Web NFC Records

[web-nfc] Provide option for suspending NFC watchers when "push a message" algorithm is not completed

[web-nfc] Pull Request: Add more examples and improve existing ones

[web-nfc] Pull Request: Change object to Dictionary. Modify receive steps to parse JSON content.

[web-nfc] Pull Request: Change type of timeout to unrestricted double fix #81

[web-nfc] Pull Request: Fix examples: remove JSON.stringify and parse. Fix the receive steps.

[web-nfc] Pull Request: Fix TAG review comments.

[web-nfc] Pull Request: Web NFC snapshot release 12 November 2015

[web-nfc] Security review

[web-nfc] Should the NFCPushTarget dictionary member be required

[web-nfc] Should there be two pushMessage methods or not

[web-nfc] TAG review

Closed: [web-nfc] add a cancelAll() instead of cancelPush()

Closed: [web-nfc] Add method for clearing all watches?

Closed: [web-nfc] Avoid resemblance with postMessage

Closed: [web-nfc] Avoid using Adapter in API

Closed: [web-nfc] can pushMessage avoid pushing a sequence?

Closed: [web-nfc] cancelPush should return Promise<void>

Closed: [web-nfc] Clamp NFCPushOptions.timeout and provide default values

Closed: [web-nfc] Consider removing .nfc namespace

Closed: [web-nfc] Consider using mediaType instead of type, type for kind

Closed: [web-nfc] Define the same NFCMessage both for push and read

Closed: [web-nfc] Make NFCPushOptions optional for pushMessage

Closed: [web-nfc] More flexible parameter to push()

Closed: [web-nfc] Potentially abstracting the payload contents a bit more from the NDEF records and from the Web NFC Records

Closed: [web-nfc] Provide option for suspending NFC watchers when "push a message" algorithm is not completed

Closed: [web-nfc] Should the NFCPushTarget dictionary member be required

Closed: [web-nfc] Should there be two pushMessage methods or not

Closed: [web-nfc] TAG review

Closed: [web-nfc] watch API should have the options dictionary as a second parameter

Help on using Web NFC Api from javascript

Minutes from the Web NFC F2F

New snapshot released

New snapshot released (was: TAG review feedback addressed - please review by 11 Nov 2015)

TAG review feedback addressed - please review by 11 Nov 2015

Web NFC Security Context?

Welcome to the Web NFC Community Group

Last message date: Tuesday, 24 November 2015 11:59:56 UTC