- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Aug 2015 15:57:52 +0000
- To: public-web-nfc@w3.org
[allowed to show a popup](https://html.spec.whatwg.org/multipage/browsers.html#allowed-to-show-a-popup) just says > The task in which the algorithm is running was queued by an algorithm that was allowed to show a popup, and the chain of such algorithms started within a user-agent defined timeframe. It gives some example times, but doesn't suggest a particular length for UAs to use. In Bluetooth, we have a timeout hidden in "perform the General Discovery Procedure", which in the BT spec includes "should continue for a minimum of T<sub>GAP</sub>(gen_disc_scan_min).", which defined as 10.24s. Does the NFC spec have any default timeouts? -- GitHub Notif of comment by jyasskin See https://github.com/w3c/web-nfc/issues/35#issuecomment-132258366
Received on Tuesday, 18 August 2015 15:57:56 UTC