Hi!
On 7/16/14, 1:24 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jul 15, 2014 at 12:28 AM, Ian Hickson i...@hixie.ch wrote:
Introducing a new API that literally doesn't do anything you can't
already do is a pretty high cost, IMHO.
It seems there are some potential differences:
Ian and
On Tue, Jul 15, 2014 at 12:28 AM, Ian Hickson i...@hixie.ch wrote:
They can use window.open() today. It's just that it causes a bit of
flicker for now. IMHO the flicker is just a bug we should fix.
Introducing a new API that literally doesn't do anything you can't already
do is a pretty high
Hi!
On 7/14/14, 7:42 PM, Ian Hickson i...@hixie.ch wrote:
On Sun, 13 Jul 2014, Adam Barth wrote:
== Use Case ==
A web site wants to launch an external protocol handler. For example,
a web site might want to launch PuTTY via the ssh scheme.
window.open('ssh://...');
I'll look at this in
On Mon, Jul 14, 2014 at 4:26 AM, Adam Barth w...@adambarth.com wrote:
The launchURL() method requests that the User Agent launch the
protocol handler for the specified URL. If the User Agent itself is
the registered protocol handler for |url|, then the User Agent should
open the requested URL
On 7/14/14, 3:35 AM, Anne van Kesteren wrote:
Is this observably different from
a target=_blank rel=noreferrer
somehow?
I think for a sandboxed iframe it might be...
Which raises a separate question, by the way: should a sandboxed iframe
(without allow-popups, in case that matters) be
Hi!
On 7/14/14, 7:40 AM, Michael[tm] Smith m...@w3.org wrote:
Adam Barth w...@adambarth.com, 2014-07-13 22:30 -0700:
On Sun, Jul 13, 2014 at 8:05 PM, Michael[tm] Smith m...@w3.org wrote:
It proposed a method that includes a successCallback
noHandlerCallback:
navigator.launchUri(uri,
On Mon, Jul 14, 2014 at 3:47 PM, Konstantin Welke
konstantin.we...@citrix.com wrote:
How we use it:
* We try to launch our native application using a custom URI scheme
* If successful, we show some “success” UI
* If no handler installed, the user gets a download
* If we don’t get a callback
Hi Anne!
On 7/14/14, 4:44 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Jul 14, 2014 at 3:47 PM, Konstantin Welke
konstantin.we...@citrix.com wrote:
How we use it:
* We try to launch our native application using a custom URI scheme
* If successful, we show some “success” UI
* If no
On Mon, Jul 14, 2014 at 5:44 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Jul 14, 2014 at 3:47 PM, Konstantin Welke
konstantin.we...@citrix.com wrote:
How we use it:
* We try to launch our native application using a custom URI scheme
* If successful, we show some “success” UI
*
On Mon, Jul 14, 2014 at 12:35 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Jul 14, 2014 at 4:26 AM, Adam Barth w...@adambarth.com wrote:
The launchURL() method requests that the User Agent launch the
protocol handler for the specified URL. If the User Agent itself is
the registered
; ann...@annevk.nl; bzbar...@mit.edu
Cc: wha...@whatwg.org; Ben Johnson
Subject: Re: [whatwg] Proposal: navigator.launchURL
Hi!
On 7/14/14, 7:40 AM, Michael[tm] Smith m...@w3.org wrote:
Adam Barth w...@adambarth.com, 2014-07-13 22:30 -0700:
On Sun, Jul 13, 2014 at 8:05 PM, Michael[tm] Smith m...@w3
On Sun, 13 Jul 2014, Adam Barth wrote:
== Use Case ==
A web site wants to launch an external protocol handler. For example,
a web site might want to launch PuTTY via the ssh scheme.
window.open('ssh://...');
I'll look at this in more detail in due course, but FWIW this appears to
be more
On Mon, Jul 14, 2014 at 10:42 AM, Ian Hickson i...@hixie.ch wrote:
On Sun, 13 Jul 2014, Adam Barth wrote:
== Use Case ==
A web site wants to launch an external protocol handler. For example,
a web site might want to launch PuTTY via the ssh scheme.
window.open('ssh://...');
I'll look at
On Mon, 14 Jul 2014, Adam Barth wrote:
The difference is that window.open opens a new browser window even if
the URL is handled by an external protocol handler. Even if we changing
current browsers to detect whether the URL will be handled by an
external protocol handler before opening
On Mon, Jul 14, 2014 at 2:10 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 14 Jul 2014, Adam Barth wrote:
The difference is that window.open opens a new browser window even if
the URL is handled by an external protocol handler. Even if we changing
current browsers to detect whether the URL
On Mon, 14 Jul 2014, Adam Barth wrote:
I'm skeptical of features that only have a benefit during a short
transition phase. Suppose it's five years from now and now everyone
implements window.open() in this cleaner way and everyone also has
launchURL(). Why is it good that we have
On Mon, Jul 14, 2014 at 3:28 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 14 Jul 2014, Adam Barth wrote:
I'm skeptical of features that only have a benefit during a short
transition phase. Suppose it's five years from now and now everyone
implements window.open() in this cleaner way and
Adam Barth w...@adambarth.com, 2014-07-13 19:26 -0700:
== Use Case ==
A web site wants to launch an external protocol handler. For example,
a web site might want to launch PuTTY via the ssh scheme.
[...]
== Proposal ==
partial interface NavigatorContentUtils {
void
On Sun, Jul 13, 2014 at 8:05 PM, Michael[tm] Smith m...@w3.org wrote:
Adam Barth w...@adambarth.com, 2014-07-13 19:26 -0700:
== Use Case ==
A web site wants to launch an external protocol handler. For example,
a web site might want to launch PuTTY via the ssh scheme.
[...]
== Proposal ==
Adam Barth w...@adambarth.com, 2014-07-13 22:30 -0700:
On Sun, Jul 13, 2014 at 8:05 PM, Michael[tm] Smith m...@w3.org wrote:
[...]
It proposed a method that includes a successCallback
noHandlerCallback:
navigator.launchUri(uri, successCallback, noHandlerCallback)
No, I missed
20 matches
Mail list logo
