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

IDL for NFCRecordData #52

Closed
riju opened this issue Sep 21, 2015 · 3 comments
Closed

IDL for NFCRecordData #52

riju opened this issue Sep 21, 2015 · 3 comments

Comments

@riju
Copy link
Collaborator

riju commented Sep 21, 2015

From [1], it looks like NFCRecordData is changing from "any" to
typedef (DOMString or unrestricted double or object or ArrayBuffer) NFCRecordData;

I had a quick look at the web-idl spec, http://heycam.github.io/webidl/#idl-union
and it looks like the above IDL is valid. But for Blink's IDL, at least as of now, Object is not supported as an union member.
I can raise the issue at https://code.google.com/p/chromium/issues/detail?id=240176

[1] https://github.com/w3c/web-nfc/pull/50/files#diff-eacf331f0ffc35d4b482f1d15a887d3bR1032

@zolkis
Copy link
Contributor

zolkis commented Sep 21, 2015

Should we switch back to any? Or could you use any just in Blink instead of the explicit union (knowing this is an issue due to Blink implementation?). I'd suggest the latter.

@riju
Copy link
Collaborator Author

riju commented Sep 22, 2015

We can do the latter, and when the Blink IDL issue is solved, switch back to NFCRecordData.

@anssiko
Copy link
Member

anssiko commented Sep 22, 2015

Given this appears to be an implementation related issue, I'll close this.

@anssiko anssiko closed this as completed Sep 22, 2015
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

No branches or pull requests

3 participants