Re: [web-nfc] Allow a NFC tap to load a URL with NFC message payload passed to the page (#78)

There seem to be several issues in this issue.  
The [original comment](https://github.com/w3c/web-nfc/issues/78#issue-113714986) seems to be loading a URL from the first record in a browser page and make the tag content available to that page.

We don't have anything on that yet.

There was a related [use-case discussion](https://github.com/w3c/web-nfc/issues/78#issuecomment-205942295) that was given a [solution](https://github.com/w3c/web-nfc/issues/78#issuecomment-206775904).

Then there was the absolute-URL discussion. We handled that wrong, now fixed. Android handles it in a special way. That was a side-kick.

The example above exposes the tag data in a discovery event - the problem is the tag has not been _discovered_, it's been already _read_ by the time the script gets to it.

In the original use case, when the page loads the tag has already been read, the question being how to provide that content to the page (bootstrapped from the same tag) without making another read (which is an option, too).

Kenneth's `referringNDEF` [suggestion](https://github.com/w3c/web-nfc/issues/78#issuecomment-545424059) seems like a better match to this particular use case.

However, I can see that we could redesign the API for the better, and in the same time aim low level. In that case IMHO we'll end up with a (potentially simplified) Android API with events and intents etc.

-- 
GitHub Notification of comment by zolkis
Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/78#issuecomment-546857844 using your GitHub account

Received on Monday, 28 October 2019 09:15:09 UTC