- From: Alex Russell <notifications@github.com>
- Date: Fri, 08 May 2015 16:19:52 -0700
- To: w3c/manifest <manifest@noreply.github.com>
Received on Friday, 8 May 2015 23:20:29 UTC
I don't think this needs to happen synchronously in the page load process. Chrome is happy to fetch the manifest asynchronously and prompt the user whenever the data comes back. Since we _also_ enforce an engagement check (i.e., you never, ever see the prompt the first time you visit), the async nature isn't a problem for us. Strongly suggest that other vendors consider doing the same, if only to avoid browser UI being used in a spammy way. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/364#issuecomment-100392422
Received on Friday, 8 May 2015 23:20:29 UTC