Support "registerProtocolHandler" in WebKit2

classic Classic list List threaded Threaded
27 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Support "registerProtocolHandler" in WebKit2

Gyuyoung Kim
Hello,

I would like to listen what do you think to support 'registerProtocolHandler' in WebKit2.

This feature is to execute web content through registered custom protocol.
- For example, web content can register "mailto" custom protocol using this feature,
    <script>
        navigator.registerProtocolHandler("mailto",
                                          "https://mail.naver.com/",
                                          "Web Mail");
    </script>

    <html>
    <head>
        <title>Web Protocol Handler Sample - Test</title>
    </head>
        <body>
            <p>Send an email : <a href="mailto://">this !</a></p>
        </body>
    </html>

Besides this feature has been supported by Mozilla and Chromium (From Mozilla 3.0, Chromium 13).

The feature is included in the W3C recommendation 28 released on Oct. 2014.

IIRC, some WebKit1 ports supported this feature though, those ports were deprecated. Now WebKit port supports this feature no more.

There is a very old bug to support this feature though, it wasn't maintained so far. Recently I updated it based on latest WebKit.

Feel free to give me any feedback about this feature.

Gyuyoung.

_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Benjamin Poulain
Looks llke nobody objects. Please make sure to #ifdef everything and disable the feature on OS X and iOS.

What is your plan for testing?

On 5/19/15 6:31 PM, Gyuyoung Kim wrote:
Hello,

I would like to listen what do you think to support 'registerProtocolHandler' in WebKit2.

This feature is to execute web content through registered custom protocol.
- For example, web content can register "mailto" custom protocol using this feature,
    <script>
        navigator.registerProtocolHandler("mailto",
                                          "https://mail.naver.com/",
                                          "Web Mail");
    </script>

    <html>
    <head>
        <title>Web Protocol Handler Sample - Test</title>
    </head>
        <body>
            <p>Send an email : <a href=[hidden email]>this !</a></p>
        </body>
    </html>

Besides this feature has been supported by Mozilla and Chromium (From Mozilla 3.0, Chromium 13).

The feature is included in the W3C recommendation 28 released on Oct. 2014.

IIRC, some WebKit1 ports supported this feature though, those ports were deprecated. Now WebKit port supports this feature no more.

There is a very old bug to support this feature though, it wasn't maintained so far. Recently I updated it based on latest WebKit.

Feel free to give me any feedback about this feature.

Gyuyoung.


_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev


_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Gyuyoung Kim
Hi Benjamin,

> Looks llke nobody objects. Please make sure to #ifdef everything and disable the feature on OS X and iOS.

Ok, let me add #ifdef guard for WK2 ports which don't use this feature.


There are already basic test cases for this feature. But I think this isn't enough to test all use cases.

After landing WK2 implementation, I'm going to improve the test cases or add new tests for some use cases.

Thanks,
Gyuyoung.


On Thu, May 21, 2015 at 3:32 PM, Benjamin Poulain <[hidden email]> wrote:
Looks llke nobody objects. Please make sure to #ifdef everything and disable the feature on OS X and iOS.

What is your plan for testing?


On 5/19/15 6:31 PM, Gyuyoung Kim wrote:
Hello,

I would like to listen what do you think to support 'registerProtocolHandler' in WebKit2.

This feature is to execute web content through registered custom protocol.
- For example, web content can register "mailto" custom protocol using this feature,
    <script>
        navigator.registerProtocolHandler("mailto",
                                          "https://mail.naver.com/",
                                          "Web Mail");
    </script>

    <html>
    <head>
        <title>Web Protocol Handler Sample - Test</title>
    </head>
        <body>
            <p>Send an email : <a href="mailto://">this !</a></p>
        </body>
    </html>

Besides this feature has been supported by Mozilla and Chromium (From Mozilla 3.0, Chromium 13).

The feature is included in the W3C recommendation 28 released on Oct. 2014.

IIRC, some WebKit1 ports supported this feature though, those ports were deprecated. Now WebKit port supports this feature no more.

There is a very old bug to support this feature though, it wasn't maintained so far. Recently I updated it based on latest WebKit.

Feel free to give me any feedback about this feature.

Gyuyoung.


_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev


_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev



_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Anders Carlsson-4
In reply to this post by Benjamin Poulain

On May 20, 2015, at 11:32 PM, Benjamin Poulain <[hidden email]> wrote:

Looks llke nobody objects. 

That’s not true. From the bug:

[hidden email] 2015-05-15 10:12:54 PDT
Support for navigator.registerProtocolHandler/unregisterProtocolHandler is not something we want to support in WebKit2 at this time as we are not confident it is a good Web API. This might be a good conversation for webkit-dev.


I agree with Sam.

- Anders



_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Gyuyoung Kim
Hi Anders,

yes, Sam didn't like to support this feature. However, as I said, I think this feature has been shipped by Firefox and Chrome browsers.
Besides It seems to me that web application will need to use this feature in near future. However I know we can't support new feature
without WK2 owner's agreement.

I wonder if it is impossible to add new feature to WK2 as an experimental feature with #ifdef guard or other better method.

Gyuyoung.

On Fri, May 22, 2015 at 1:25 AM, Anders Carlsson <[hidden email]> wrote:

On May 20, 2015, at 11:32 PM, Benjamin Poulain <[hidden email]> wrote:

Looks llke nobody objects. 

That’s not true. From the bug:

[hidden email] 2015-05-15 10:12:54 PDT
Support for navigator.registerProtocolHandler/unregisterProtocolHandler is not something we want to support in WebKit2 at this time as we are not confident it is a good Web API. This might be a good conversation for webkit-dev.


I agree with Sam.

- Anders



_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev



_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Anne van Kesteren
In reply to this post by Anders Carlsson-4
On Fri, May 22, 2015 at 1:25 AM, Anders Carlsson <[hidden email]> wrote:
> Sam Weinig 2015-05-15 10:12:54 PDT:
>> Support for navigator.registerProtocolHandler/unregisterProtocolHandler is not something we want to support in WebKit2 at this time as we are not confident it is a good Web API. This might be a good conversation for webkit-dev.
>
> I agree with Sam.

So what else should web-based email or IRC clients or some such use to
integrate with sites that offer mailto and irc URLs? Especially for
email it seems like a worthwhile thing to solve. And that there's no
cross-browser way to do it in 2015 is somewhat of a shame.


--
https://annevankesteren.nl/
_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Maciej Stachowiak

On May 21, 2015, at 7:38 PM, Anne van Kesteren <[hidden email]> wrote:

On Fri, May 22, 2015 at 1:25 AM, Anders Carlsson <[hidden email]> wrote:
Sam Weinig 2015-05-15 10:12:54 PDT:
Support for navigator.registerProtocolHandler/unregisterProtocolHandler is not something we want to support in WebKit2 at this time as we are not confident it is a good Web API. This might be a good conversation for webkit-dev.

I agree with Sam.

So what else should web-based email or IRC clients or some such use to
integrate with sites that offer mailto and irc URLs? Especially for
email it seems like a worthwhile thing to solve. And that there's no
cross-browser way to do it in 2015 is somewhat of a shame.

I think it’s useful to have an API for the "mailto" use case. A lot of people use webmail as their default mail client, and it seems nice to make mailto: links do the right thing for them. We do allow changing the default Mail reader to a native app, at least on Mac. I would almost consider having navigator.registerProtocolHandler just for that use case.

On the face of it, the registerProtocolHandler API seems more general than necessary, but the actual spec for it has a whitelist of specific schemes, most of which seem reasonable for this kind of purpose: https://html.spec.whatwg.org/#custom-handlers

I am curious what Sam and Anders dislike about this API, and whether it might be something we’d want to support at least with a more restricted set of schemes.

(I am more dubious of the content handler aspect.)

Regards,
Maciej


_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Anne van Kesteren
On Fri, May 22, 2015 at 12:26 PM, Maciej Stachowiak <[hidden email]> wrote:
> (I am more dubious of the content handler aspect.)

Agreed, especially as it requires the service to download the resource
again. For that use case we need something smarter where you can pass
along an object/stream of sorts I think.


--
https://annevankesteren.nl/
_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Gyuyoung Kim
>On the face of it, the registerProtocolHandler API seems more general than necessary, but the actual spec for it has a whitelist of specific schemes, most of which seem reasonable for this kind of >purpose:https://html.spec.whatwg.org/#custom-handlers

Yes, the custom-handlers specification only allows us to use specific schemes, and current WebCore implementation was implemented based on the spec.
Current supported schemes are only below,

        "bitcoin", "geo", "im", "irc", "ircs", "magnet", "mailto", "mms", "news", "nntp", "sip", "sms", "smsto", "ssh", "tel", "urn", "webcal", "wtai", "xmpp"


>> (I am more dubious of the content handler aspect.)

>Agreed, especially as it requires the service to download the resource
>again. For that use case we need something smarter where you can pass
>along an object/stream of sorts I think.

I also don't want to support the "content handler" feature at the moment. The feature might be more clear and mature. The patch of Bug 92749 only supports registerProtocolHandler,
and unregisterProtocolHandler and isProtocolHandlerRegistered are supported as optional.


Gyuyoung.


On Fri, May 22, 2015 at 12:50 PM, Anne van Kesteren <[hidden email]> wrote:
On Fri, May 22, 2015 at 12:26 PM, Maciej Stachowiak <[hidden email]> wrote:
> (I am more dubious of the content handler aspect.)

Agreed, especially as it requires the service to download the resource
again. For that use case we need something smarter where you can pass
along an object/stream of sorts I think.


--
https://annevankesteren.nl/
_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev


_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Anne van Kesteren
On Fri, May 22, 2015 at 1:50 PM, Gyuyoung Kim <[hidden email]> wrote:
> I also don't want to support the "content handler" feature at the moment.
> The feature might be more clear and mature. The patch of Bug 92749 only
> supports registerProtocolHandler,
> and unregisterProtocolHandler and isProtocolHandlerRegistered are supported
> as optional.
>
>  https://bugs.webkit.org/show_bug.cgi?id=92749

Quickly scanning the bug I couldn't figure out whether you added hooks
to HTML's navigate algorithm or Fetch' fetch algorithm. In particular,
see the discussion in this bug:

  https://www.w3.org/Bugs/Public/show_bug.cgi?id=24091

My personal opinion is that these schemes should only have an effect
if you navigate to them, not if you fetch them (the latter should
result in a network error in my opinion).


--
https://annevankesteren.nl/
_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Gyuyoung Kim
> Quickly scanning the bug I couldn't figure out whether you added hooks
to HTML's navigate algorithm or Fetch' fetch algorithm. In particular,
see the discussion in this bug:

  https://www.w3.org/Bugs/Public/show_bug.cgi?id=24091

My personal opinion is that these schemes should only have an effect
if you navigate to them, not if you fetch them (the latter should
result in a network error in my opinion).

Current implementation doesn't hook to HTML's navigation directly. We delegate the html navigation(or call native application) to application.
Application is able to decide to navigate the given html page or execute native application through the patch. As far as I know, Chrome also has
similar implementation.

If this feature can be landed, I have a plan to test this scenario based on mock implementation.

Gyuyoung.


On Fri, May 22, 2015 at 5:52 PM, Anne van Kesteren <[hidden email]> wrote:
On Fri, May 22, 2015 at 1:50 PM, Gyuyoung Kim <[hidden email]> wrote:
> I also don't want to support the "content handler" feature at the moment.
> The feature might be more clear and mature. The patch of Bug 92749 only
> supports registerProtocolHandler,
> and unregisterProtocolHandler and isProtocolHandlerRegistered are supported
> as optional.
>
https://bugs.webkit.org/show_bug.cgi?id=92749

Quickly scanning the bug I couldn't figure out whether you added hooks
to HTML's navigate algorithm or Fetch' fetch algorithm. In particular,
see the discussion in this bug:

  https://www.w3.org/Bugs/Public/show_bug.cgi?id=24091

My personal opinion is that these schemes should only have an effect
if you navigate to them, not if you fetch them (the latter should
result in a network error in my opinion).


--
https://annevankesteren.nl/


_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Gyuyoung Kim
In reply to this post by Anne van Kesteren
> Quickly scanning the bug I couldn't figure out whether you added hooks
to HTML's navigate algorithm or Fetch' fetch algorithm. In particular,
see the discussion in this bug:

  https://www.w3.org/Bugs/Public/show_bug.cgi?id=24091

My personal opinion is that these schemes should only have an effect
if you navigate to them, not if you fetch them (the latter should
result in a network error in my opinion).

Current implementation doesn't hook to HTML's navigation directly. We delegate the html navigation(or call native application) to application.
Application is able to decide to navigate the given html page or execute native application through the patch. As far as I know, Chrome also has
similar implementation.

If this feature can be landed, I have a plan to test this scenario based on mock implementation.

Gyuyoung.

On Fri, May 22, 2015 at 5:52 PM, Anne van Kesteren <[hidden email]> wrote:
On Fri, May 22, 2015 at 1:50 PM, Gyuyoung Kim <[hidden email]> wrote:
> I also don't want to support the "content handler" feature at the moment.
> The feature might be more clear and mature. The patch of Bug 92749 only
> supports registerProtocolHandler,
> and unregisterProtocolHandler and isProtocolHandlerRegistered are supported
> as optional.
>
https://bugs.webkit.org/show_bug.cgi?id=92749

Quickly scanning the bug I couldn't figure out whether you added hooks
to HTML's navigate algorithm or Fetch' fetch algorithm. In particular,
see the discussion in this bug:

  https://www.w3.org/Bugs/Public/show_bug.cgi?id=24091

My personal opinion is that these schemes should only have an effect
if you navigate to them, not if you fetch them (the latter should
result in a network error in my opinion).


--
https://annevankesteren.nl/


_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Anne van Kesteren
In reply to this post by Gyuyoung Kim
On Fri, May 22, 2015 at 6:43 PM, Gyuyoung Kim <[hidden email]> wrote:
> Current implementation doesn't hook to HTML's navigation directly. We
> delegate the html navigation(or call native application) to application.
> Application is able to decide to navigate the given html page or execute
> native application through the patch. As far as I know, Chrome also has
> similar implementation.

Okay, so

  <img src=mailto:...>

results in a network error and not a fetch to the registered URL?


--
https://annevankesteren.nl/
_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Gyuyoung Kim
Hi Anne,

I need to verify the behaviour using the patch though, I think the registered URL isn't fetched under current patch of Bug 92749.
However I need to check if the registered URL is passed to application under the patch's implementation. If this feature will be landed to WK2,
it would be good if we add a test to check it. Let me do it.

Gyuyoung.

On Sat, May 23, 2015 at 9:55 AM, Anne van Kesteren <[hidden email]> wrote:
On Fri, May 22, 2015 at 6:43 PM, Gyuyoung Kim <[hidden email]> wrote:
> Current implementation doesn't hook to HTML's navigation directly. We
> delegate the html navigation(or call native application) to application.
> Application is able to decide to navigate the given html page or execute
> native application through the patch. As far as I know, Chrome also has
> similar implementation.

Okay, so

  <img src=mailto:...>

results in a network error and not a fetch to the registered URL?


--
https://annevankesteren.nl/


_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Gyuyoung Kim
It seem to me there are both agreements and objections to support this feature in WebKit2.
It looks many web contents have already used some custom schemes as 'mailto://', and In my humble opinion, the feature
will be able to improve the usage of the custom scheme. Besides we can control the supported custom schemes because
the feature only supports pre-defined custom schemes. Web content is only able to use the pre-defined custom schemes.
In my opinion, it would be good if the feature is supported by WebKit2 although it is added as an experimental feature using #ifdef.

However If WK2 owners still think this feature needs to be more stable, I will wait until they agree it.

Gyuyoung.

On Sat, May 23, 2015 at 12:36 PM, Gyuyoung Kim <[hidden email]> wrote:
Hi Anne,

I need to verify the behaviour using the patch though, I think the registered URL isn't fetched under current patch of Bug 92749.
However I need to check if the registered URL is passed to application under the patch's implementation. If this feature will be landed to WK2,
it would be good if we add a test to check it. Let me do it.

Gyuyoung.

On Sat, May 23, 2015 at 9:55 AM, Anne van Kesteren <[hidden email]> wrote:
On Fri, May 22, 2015 at 6:43 PM, Gyuyoung Kim <[hidden email]> wrote:
> Current implementation doesn't hook to HTML's navigation directly. We
> delegate the html navigation(or call native application) to application.
> Application is able to decide to navigate the given html page or execute
> native application through the patch. As far as I know, Chrome also has
> similar implementation.

Okay, so

  <img src=mailto:...>

results in a network error and not a fetch to the registered URL?


--
https://annevankesteren.nl/



_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Michael Catanzaro
In reply to this post by Gyuyoung Kim
On Wed, 2015-05-20 at 10:31 +0900, Gyuyoung Kim wrote:
> I would like to listen what do you think to support
> 'registerProtocolHandler' in WebKit2.
>
> This feature is to execute web content through registered custom
> protocol.

Hi,

I think this would be useful for GNOME. One of our goals is for the
user to be able to set GMail as the default mail application in System
Settings. If the user visits gmail.com and it attempts to register
itself as a mailto:// handler, I envision the WebKitGTK+ would fire a
signal that would trigger Epiphany to display an info bar to ask the
user for approval. If the user approves the registration, we would go
one step further: we'd create a new web application for GMail and in
the desktop file indicate support for the MIME type x-scheme
-handler/mailto (or if the user already has a GMail web application,
modify the desktop file to add that MIME type). The user would then be
able to set the GMail web app as the default mail application
systemwide.

We would restrict this functionality to HTTPS sites only. I'd greatly
prefer that restriction to be enforced by WebKit rather than
implementing that policy in Epiphany.

Michael
_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Gyuyoung Kim
In order to support the use case on Epiphany browser, we need to support this feature on WK2 first.
Besides, as far as I know, EFL browser will have similar use-case by using this feature. Thus, in my humble opinion, similar use cases
can be more required in near future.

Gyuyoung.

On Tue, Jun 2, 2015 at 9:21 PM, Michael Catanzaro <[hidden email]> wrote:
On Wed, 2015-05-20 at 10:31 +0900, Gyuyoung Kim wrote:
> I would like to listen what do you think to support
> 'registerProtocolHandler' in WebKit2.
>
> This feature is to execute web content through registered custom
> protocol.

Hi,

I think this would be useful for GNOME. One of our goals is for the
user to be able to set GMail as the default mail application in System
Settings. If the user visits gmail.com and it attempts to register
itself as a mailto:// handler, I envision the WebKitGTK+ would fire a
signal that would trigger Epiphany to display an info bar to ask the
user for approval. If the user approves the registration, we would go
one step further: we'd create a new web application for GMail and in
the desktop file indicate support for the MIME type x-scheme
-handler/mailto (or if the user already has a GMail web application,
modify the desktop file to add that MIME type). The user would then be
able to set the GMail web app as the default mail application
systemwide.

We would restrict this functionality to HTTPS sites only. I'd greatly
prefer that restriction to be enforced by WebKit rather than
implementing that policy in Epiphany.

Michael
_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev


_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Darin Adler
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
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Michael Catanzaro
On Sun, 2015-06-07 at 17:39 -0700, Darin Adler wrote:
> As one next step in the discussion, is there anyone that wants to
> present a use case for a protocol other than mailto?

irc:// would be useful for those who don't like desktop clients.

_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
Reply | Threaded
Open this post in threaded view
|

Re: Support "registerProtocolHandler" in WebKit2

Gyuyoung Kim
On Mon, Jun 8, 2015 at 12:02 PM, Michael Catanzaro <[hidden email]> wrote:
On Sun, 2015-06-07 at 17:39 -0700, Darin Adler wrote:
> As one next step in the discussion, is there anyone that wants to
> present a use case for a protocol other than mailto?

irc:// would be useful for those who don't like desktop clients.


"geo:" would be useful for people who want to use map application as well.

Gyuyoung.


_______________________________________________
webkit-dev mailing list
[hidden email]
https://lists.webkit.org/mailman/listinfo/webkit-dev
12