[Webkit-unassigned] [Bug 204558] Expose public API for registering URL schemes as secure and as bypassing content security policy

[bugzilla-daemon at webkit.org]

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

Kurt Revis <krevis at figma.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |krevis at figma.com

--- Comment #4 from Kurt Revis <krevis at figma.com> ---
Seconding that this still appears to be a problem (as of 2022 and iOS 16) and would still be useful. 

A custom URL scheme would be a great way to quickly transfer data between an app and a WKWebView inside of it, without the overhead of serializing to a JS string. But since it's unusable in HTTPS pages, that's a dealbreaker.

(Using the private method `-[WKProcessPool _registerURLSchemeAsSecure:]` works fine, but of course we can't ship that.)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220914/440e798e/attachment.htm>