[Webkit-unassigned] [Bug 73638] [EFL] Implement 'registerProtocolHandler' function

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=73638





--- Comment #45 from Dongwoo Joshua Im (dwim) <dw.im at samsung.com>  2012-05-21 21:01:35 PST ---
(In reply to comment #44)
> (In reply to comment #43)
> > (From update of attachment 143166 [details] [details])
> > View in context: https://bugs.webkit.org/attachment.cgi?id=143166&action=review
> > 
> > > Source/WebKit/efl/ewk/ewk_view.h:320
> > > +    const char *base_url; /**< Reference to the resolved url if the url is relative url. (eg. "https://www.currenthost.com/") */
> > > +    const char *url; /**< Reference to the url which will handle the given protocol. (eg. "https://www.example.com/?uri=%s") */
> > 
> > One last thing regarding these two comments: I don't think base_url has anything to do with relative URLs, and url itself may not be a full URL.
> > 
> > Using the example from <http://www.w3.org/TR/html5/system-state-and-capabilities.html#custom-handlers>, if a user visits http://www.example.com/foo/bar.html and this page calls navigator.registerProtocolHandler('application/x-soup', 'soup?url=%s', 'SoupWeb'):
> >  - base_url will be "http://www.example.com/"
> >  - url will be "soup?url=%s"
> 
> As I know, url could be relative url, or not.
> 

OK.

Regarding the discussion on the irc,
I will use the scheme, url, and title which are in the W3C spec.

I will upload the new patch soon.
> The url is a releative url in the example that you mentioned. 
> 
> When I wrote the comments, I was thinking the url is absolute path of url, not relative.
> 
> Do you want me to change the comment regarding your example?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.