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

Implementation status page #455

Closed
beaufortfrancois opened this issue Nov 27, 2019 · 8 comments
Closed

Implementation status page #455

beaufortfrancois opened this issue Nov 27, 2019 · 8 comments
Labels
Origin Trial Issues that would be good to solve before OT

Comments

@beaufortfrancois
Copy link
Collaborator

It would be great if this repository would host an implementation status page so that web developers interested in Web NFC could quickly see which features are implemented in various browsers?

See https://github.com/w3c/picture-in-picture/blob/master/implementation-status.md and https://github.com/WebBluetoothCG/web-bluetooth/blob/master/implementation-status.md

@leonhsl Could you list in this issue the currently missing/implemented features we would use to populate a table?

@beaufortfrancois
Copy link
Collaborator Author

For instance, "peer" NDEFPushTarget is not implemented in Chromium.

@leonhsl
Copy link
Contributor

leonhsl commented Dec 2, 2019

In Chromium:

  • Not support any operations on NFC peers, just NFC tags for now.

  • Not support reading/writing for several well-known type records.

     1. Smart poster records
     2. Signature records
     3. Handover records
     4. Local type name (acting as embedded records)
    
  • Not support writing embedded records, i.e. NDEFRecordInit#data
    does not accept NDEFMessageInit yet.

  • Not support triggering NDEFReader#onerror to notify errors that happened while trying to read a nfc tag, e.g. the tag coming nearby is not ndef-compatible, or some other IO errors.

  • Not support calling NDEFReader#scan() a second time on the reader object which is already in the middle of scan().

@leonhsl
Copy link
Contributor

leonhsl commented Dec 2, 2019

I looked through spec and code and got the above list for now. May update later.

@riju
Copy link
Collaborator

riju commented Dec 2, 2019

Thanks @beaufortfrancois and @leonhsl, I am sure many developers will try WebNFC and pointing them to a single source of truth is a good idea.

We should definitely list features like (smart posters, signature records, etc ) which we might implement if we feel there's a critical mass of users. It would be too complicated to add "voting" I guess, but we will get the pulse more effectively.

@leonhsl Feel free to add short notes and last updated also in the implementation.md like here.

@beaufortfrancois
Copy link
Collaborator Author

I've noted "overwrite" was not supported as well in Chromium for now.

@kenchris kenchris added the Origin Trial Issues that would be good to solve before OT label Jan 8, 2020
@leonhsl
Copy link
Contributor

leonhsl commented Jan 24, 2020

Update to #455 (comment).

Now, in Chromium:

  • Not support any operations on NFC peers, just NFC tags for now.

  • Not support reading/writing for several well-known type records.

     1. Smart poster records
     2. Signature records
     3. Handover records
     4. Local type name (acting as embedded records)
    
  • Not support calling NDEFReader#scan() a second time on the reader object which is already in the middle of scan().

@leonhsl
Copy link
Contributor

leonhsl commented Jan 24, 2020

Update to #455 (comment).

We already added the support for NDEFWriteOptions#overwrite.

@beaufortfrancois
Copy link
Collaborator Author

I believe this issue and https://github.com/w3c/web-nfc/blob/gh-pages/EXPLAINER.md#changes-done-after-origin-trial-ot have done the job. I'll close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Origin Trial Issues that would be good to solve before OT
Projects
None yet
Development

No branches or pull requests

4 participants