Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove request to adapters to listen to NDEF messages #484

Merged
merged 2 commits into from Dec 24, 2019

Conversation

beaufortfrancois
Copy link
Collaborator

@beaufortfrancois beaufortfrancois commented Dec 23, 2019

I think* we can remove the part where we "make a request to all NFC adapters to listen to NDEF messages" in scan promise as we're already saying that "If there are any NDEFReader instances in activated reader objects then the UA MUST listen to NDEF messages." See https://w3c.github.io/web-nfc/#listening-for-content

Note that we've already checked NFC adapter existence and if NFC connection can be established at that point.

Context: #478 (comment)


Preview | Diff

@zolkis
Copy link
Contributor

zolkis commented Dec 23, 2019

The explicit step was outlined to make clear that if there are multiple NFC adapters, all of them should be used in parallel. The UA should not make a decision which one to use.

I think that removing this would be fair but may need to clarify in the premise.

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

(or something like this).

@beaufortfrancois
Copy link
Collaborator Author

@zolkis I've updated "listening for content" section based on your feedback at d54bf27

@zolkis
Copy link
Contributor

zolkis commented Dec 24, 2019

Thank you!

@zolkis zolkis merged commit 7c1b559 into w3c:gh-pages Dec 24, 2019
@beaufortfrancois beaufortfrancois deleted the fix-request branch December 24, 2019 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants