- From: Larry Masinter <masinter@adobe.com>
- Date: Wed, 19 Sep 2012 14:48:35 -0700
- To: Adam Barth <w3c@adambarth.com>, Mark Nottingham <mnot@mnot.net>
- CC: Robin Berjon <robin@berjon.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Peter Saint-Andre <stpeter@stpeter.im>, "michel@suignard.com" <michel@suignard.com>, "tony@att.com" <tony@att.com>, "plh@w3.org" <plh@w3.org>, "adil@diwan.com" <adil@diwan.com>, "ted.ietf@gmail.com" <ted.ietf@gmail.com>, "John O'Conner" <jooconne@adobe.com>, "presnick@qualcomm.com" <presnick@qualcomm.com>, "chris@lookout.net" <chris@lookout.net>, "public-ietf-w3c@w3.org" <public-ietf-w3c@w3.org>, "public-sysapps@w3.org" <public-sysapps@w3.org>
Re http://lists.w3.org/Archives/Public/public-ietf-w3c/2012Sep/0035.html
http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html#custom-handlers
As system level APIs that persistently affect any application that uses a URL or interprets a media type, and not just the browser and site which invoked them initially, registerProtocolHandler and registerContentHandler need the security model of a system-level application.
I believe W3C should move "registerProtocolHandler" and "registerContentHandler" to the proposed Sysapps working group, http://www.w3.org/2012/05/sysapps-wg-charter.html where they can get proper attention.
Larry
--
http://larry.masinter.net
Received on Wednesday, 19 September 2012 21:49:40 UTC