Re: [web-nfc] Notification when a browsing context is closed?

For 1), in the case of document unload, which is the script execution 
environment you want to see Promises handled in? IMO developers will 
only need to handle Promises, and not the corner cases when they are 
assumed not working. IMO it is not this specification which should 
deal with this. We return a Promise: under it the implementation is 
responsible, above it the developers.

2) is invalid, no NFC transaction takes 22 hours. In most tag types it
 is sub-second. With Type 3 it could be theoretically as long as a 
minute, but in practice is also sub-second or second magnitude. If 
transmission is interrupted, you will get an error.
The concern you mention is owned by implementations, and not the spec.

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

Received on Wednesday, 7 October 2015 06:54:42 UTC