- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 24 Jan 2012 09:49:50 +0100
- To: Jonathan A Rees <rees@mumble.net>
- CC: Noah Mendelsohn <nrm@arcanedomain.com>, "www-tag@w3.org" <www-tag@w3.org>, Paul Cotton <Paul.Cotton@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Sam Ruby <rubys@intertwingly.net>
On 2012-01-24 03:10, Jonathan A Rees wrote: > I was wondering - is the registered handler supposed to work with all > applications, or just web browsers? For example, mail readers, PDF > viewers, document and spreadsheet composers - anything that exposes > actionable hyperlinks. If so then this is really an OS-level feature > and I wonder what it's doing in an HTML specification. (Especially > since browsers aren't the only containers for Javascript... right?) > What's the intended mechanism - the OS looks at the browser > configuration, or vice versa, or it doesn't matter? If not then why > not? Can general users tell the difference between a browser and the > rest of their application software suite? > > I also note that this is an awful lot like HTTP proxy server > configuration and "parental controls", both of which interfere with > URI handling. Maybe there useful analogies to the configuration and > security experience in those areas. > > Jonathan To make this work as expected, the browser will need to be registered OS-wide as handler for the URI scheme. It then can "proxy" the request to the registered web page. Best regards, Julian
Received on Tuesday, 24 January 2012 08:50:24 UTC