Re: [web-nfc] Should there be two pushMessage methods or not

To summarize, we want to:
1. Simplify the way ```push()``` is called, and not care if the push 
message refers to tag or peer: whichever is tapped first, the push 
happens there.
2. Still maintain possibility to say that the push message is meant 
only for tags, or peers.

One solution is to reintroduce ```"any"``` as ```NFCPushTarget``` 
value, and make it default.
@jyasskin you have had some issues with the value ```"any"``` (or the 
related steps) in the past, but I don't recall what it was. I will try
 to use it again and let's see if I can formulate the steps well.

-- 
GitHub Notif of comment by zolkis
See https://github.com/w3c/web-nfc/issues/73#issuecomment-153320629

Received on Tuesday, 3 November 2015 11:18:09 UTC