Re: [web-nfc] Consider removing .nfc namespace

I'm in favor of option (3).
As I mentioned before, "multiple adapters" scenario is highly 
improbable and degrades usability of API for 99.9% of use-cases.

Promise<void> selectAdapter(); function also degrades API usability.
Developers would need to think about things like:

1. Should it be called before push / watch?
2. If promise is resolved => new adapter selected or same adapter 
selected?
3. If promise is resolved and new adapter is selected what happens 
with push / watch that were invoked for old adapter?
4. If promise rejected => dialog was cancelled? Can developer still 
call push / watch?
5. If external usb adapter was selected and then physically removed, 
do we switch back to internal, do we reject all pending promises?

I'm for simple API that doesn't have quirks due to unrealistic 
scenarios.

-- 
GitHub Notif of comment by alexshalamov
See https://github.com/w3c/web-nfc/issues/67#issuecomment-151419476

Received on Tuesday, 27 October 2015 09:01:09 UTC