Re: HTML5 proposes introduction of new family of URI schemes

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.


Received on Tuesday, 24 January 2012 02:11:27 UTC