- From: Michael[tm] Smith <mike@w3.org>
- Date: Mon, 14 Jul 2014 14:40:31 +0900
- To: Adam Barth <w3c@adambarth.com>
- Cc: whatwg@whatwg.org, Ben Johnson <Ben.Johnson@citrix.com>, Konstantin Welke <Konstantin.Welke@citrix.com>
Adam Barth <w3c@adambarth.com>, 2014-07-13 22:30 -0700: > On Sun, Jul 13, 2014 at 8:05 PM, Michael[tm] Smith <mike@w3.org> wrote: [...] > > It proposed a method that includes a "successCallback" & "noHandlerCallback": > > > > navigator.launchUri(uri, successCallback, noHandlerCallback) > > No, I missed that. Looks very similar. A more modern idiom would be > to return a promise to inform the caller of success or failure. Yeah > Is there a use case for reporting success or failure? I thought about > including that, but it wasn't necessary for the use cases I'm aware > of. Konstantin mentioned: > > We would like to have a stable, well-defined API for this that also allows > > to handle the “user declined / protocol handler is not installed” case > > gracefully. As an example, the web page could show a UI to tell the user > > how to install an SSH client. http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0797.html -- Michael[tm] Smith http://people.w3.org/mike
Received on Monday, 14 July 2014 05:40:57 UTC