<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - WKWebView does not fully support custom NSURLProtocol"
href="https://bugs.webkit.org/show_bug.cgi?id=138169#c17">Comment # 17</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - WKWebView does not fully support custom NSURLProtocol"
href="https://bugs.webkit.org/show_bug.cgi?id=138169">bug 138169</a>
from <span class="vcard"><a class="email" href="mailto:beidson@apple.com" title="Brady Eidson <beidson@apple.com>"> <span class="fn">Brady Eidson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=138169#c16">comment #16</a>)
<span class="quote">> Early this year Chrome for iOS migrated from UIWebView to WKWebView.
> WKWebView gave us a huge improvement in stability, but inability to use
> custom network protocols made impossible to support the following features:
>
> Privacy
> - Block 3rd party cookies
> - Do Not Track
> - Non-ephemeral Incognito browsing (so users are not logged out if they
> background the app and the app is killed in the background.)
>
> Security
> - HSTS preloads
> - Public key pinning
> - Safe browsing
> - SHA-1 deprecation warning
>
> Other features
> - Data Saver
> - Downloads if authentication is required (no access to cookies)
> - Multiple profiles support
> - QUIC network protocol
> - WebP image format</span >
This list is full of interesting API requests, but only a few are related to this bug.
I'd urge you to make sure there are independent bug reports for each.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>