W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2014

Re: [whatwg] Proposal: navigator.launchURL

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 14 Jul 2014 21:10:20 +0000 (UTC)
To: Adam Barth <w3c@adambarth.com>
Message-ID: <alpine.DEB.2.00.1407142108480.17684@ps20323.dreamhostps.com>
Cc: whatwg@whatwg.org
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 the window, web sites won't be 
> able to feature-detect which browsers have this new behavior and 
> therefore won't be able to move away from iframe@src hacks until all the 
> browsers they care about have the behavior change.  By contrast, sites 
> can feature detect navigator.launchURL and fall back to iframe@src in 
> UAs that lack the new API.

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 both?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 14 July 2014 21:10:45 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:21 UTC