(Sorry, had this sitting in my drafts). My concern with the registerProtocolHandler() API is that it complicates an already the very complicated area of custom protocols and a good implementation requires configuration UI (to choose which of potentially multiple apps/websites you want a specific protocol to go to) that I am not sure users are in the position make.
That, coupled with the small existing usage on the web and very few (if any) reports from developers that they want this, leads me to think it isn’t a good API for us to support. From an implementation perspective I also have concerns. How is this should the registration data be managed? Can it fit in the WebSiteData model we are using for other data? Does it account for non-persistent sessions? And lastly, can we get the code size of supporting a feature like this to be smaller? - Sam > On Jun 7, 2015, at 5:39 PM, Darin Adler <da...@apple.com> wrote: > > Are we making progress in this discussion? > > Maciej stated that he thinks this is useful for mailto and I think that > Gyuyoung Kim and Michael Catanzaro stated that they want to do this. > > As one next step in the discussion, is there anyone that wants to present a > use case for a protocol other than mailto? > > Sam, Anders, you haven’t replied to the thread since Maciej made his remarks > two weeks ago. He asked what you dislike about the API. > > — Darin > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
