- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Dec 2019 21:03:15 +0000
- To: public-web-nfc@w3.org
(I'd also note that (2) and (3) don't really seem like separate steps. But it also seems like, implicitly, between them, there's something like "wait for this request to ???", so that they could be combined as something like: " If this is the first listener being set up, then make a request to all NFC adapters to listen to NDEF messages. Wait for this request to ???. If the request fails, then the UA MAY reject p with a "NotSupportedError" DOMException and abort these steps." (Though this also seems to forbid a UA from trying again if it fails once, which might be undesirable.) Likewise, it's not clear to me that step 5, currently: > If the Document of the top-level browsing context is not visible (e.g. the user navigated to another page), then the registered activated reader objects still SHOULD continue to exist, but SHOULD become paused, i.e. the UA SHOULD NOT check and use them until the Document is visible again. is really a step that happens chronologically. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/478#issuecomment-567675848 using your GitHub account
Received on Thursday, 19 December 2019 21:04:50 UTC