[Webkit-unassigned] [Bug 73177] Add Custom Content Handler

[bugzilla-daemon at webkit.org]

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





--- Comment #11 from Dongwoo Joshua Im (dwim) <dw.im at samsung.com>  2012-06-08 00:59:13 PST ---
(In reply to comment #10)
> Won't that break folks who are using that content type?  For registerProtocolHandler, we use the web+ prefix to solve this problem.

1. I'm a little bit unclear what you are concerning.

at comment #7, you are worried about new mime type.
I thought you are worried that new mime type might go to the handler rather than run on the browser itself.

If it is right, that could be maintained what I suggested at comment #9 - maintaining the blacklist.

But now at comment #10, I think you are worrying that the new mime type might not go to the handler which want to handler that mime type.



2. For registerProtocolHandler, we use "web+" prefix just like whitelist.
If a protocol start with "web+", we can add the handler even if it is not in the whitelist.

We can use similar strategy here.

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