From 1556a72a890b3d6759af9e37e633c4a58b036a90 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Beaufort?= Date: Mon, 23 Dec 2019 12:09:51 +0100 Subject: [PATCH 1/2] Remove request to adapters to listen to NDEF messages --- index.html | 8 -------- 1 file changed, 8 deletions(-) diff --git a/index.html b/index.html index cba8b2a..4120cb4 100644 --- a/index.html +++ b/index.html @@ -3429,14 +3429,6 @@

Writing or pushing content

reject |p| with a {{"NotAllowedError"}} {{DOMException}} and abort these steps. -
  • - If this is the first listener being set up, then make a request - to all NFC adapters to listen to NDEF messages. -
  • -
  • - If the request fails, then the UA MAY reject |p| with a - {{"NotSupportedError"}} {{DOMException}} and abort these steps. -
  • Add |reader| to the activated reader objects.
  • From d54bf27456e000782122f806bc5589309766ebb4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Beaufort?= Date: Tue, 24 Dec 2019 07:32:34 +0100 Subject: [PATCH 2/2] Update listening for content section --- index.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/index.html b/index.html index 4120cb4..e48a976 100644 --- a/index.html +++ b/index.html @@ -3318,7 +3318,8 @@

    Writing or pushing content

    Listening for content

    If there are any {{NDEFReader}} instances in activated reader objects - then the UA MUST listen to NDEF messages. + then the UA MUST listen to NDEF messages on all connected + NFC adapters.

    To listen for NFC content, the client MUST activate an