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

OK.

My concerns are, (1), that developers won't now know whether they'll 
have to handle rejection of pending promises on unload (explicitly 
state implementation-dependence?), and (2), that an NFC message can 
take up to 22 hours to transmit, so there can be 22 hours of 
uncertainty whether data is being transmitted if it's unstated what 
happens to in-progress transmissions on a cancelPush, a valid concern 
for the clean slate of the next document that you've mentioned.

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

Received on Tuesday, 6 October 2015 14:53:01 UTC