<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#c19">Comment # 19</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#c18">comment #18</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=138169#c17">comment #17</a>)
> > (In reply to <a href="show_bug.cgi?id=138169#c16">comment #16</a>)
> > > 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
> >
> > 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.
>
> All of the things here look very familiar to me. It looks related to
> NSURLProtocol support in a way that it enables all of those features. If
> NSURLProtocol support was introduced the developers could bring back all
> that code to implement the listed features.
>
> One could possibly create separate bugs for each of the use cases that were
> listed, and solve them with separate methods, but I think that the call from
> Sam was to list all possible use cases. This points out how the lack of
> NSURLProtocol support affected the apps that migrated (or plan to migrate)
> to WKWebView, and shows which use cases have to be dropped because they were
> based on NSURLProtocol-s.</span >
I'm not saying "stop listing your use cases here and please file a new bug on everything".
I just don't want this bug to start tracking "Here is every single gripe I have with the WKWebView API", which would be unproductive.
There's things in this list for which SPI already exists (e.g. 3rd party cookie blocking), and things in this list for which "Custom NSURLProtocol is the solution!" is not apparent to everyone.
WebP images for example: It's not at all apparent (to me, at least) why implementing a custom image format requires custom network loading. Maybe I'm missing something obvious?</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>