Bug 201563
Summary: | Allow WKWebView users to enable ITP | ||
---|---|---|---|
Product: | WebKit | Reporter: | Rajaram Gaunker <zimbabao> |
Component: | WebKit API | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | CC: | ajuma, daniel, ehsan, krzysztof.modras, mjs, webkit-bug-importer, wilander |
Priority: | P2 | Keywords: | InRadar |
Version: | Other | ||
Hardware: | iPhone / iPad | ||
OS: | All |
Rajaram Gaunker
Allow an option to enable ITP in WKWebView.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/55148360>
Maciej Stachowiak
We are reviewing approaches to this, but nothing to report just yet. We might just turn ITP on for all WKWebViews.
Krzysztof Jan Modras [:chrmod]
We also believe privacy should be by default. Many iOS app developers using WebViews have limited knowledge of the Web and their app will benefit greatly from more private default configuration.
Having an option to control ITP in WKWebView would still be beneftial in couple use cases:
- browsers may choose to roll out their own tracking prevention
- some application may experience brakage due to ITP and may prefer to disable it
Not sure to which object ITP setting belong, it may be any of those probably: WKWebViewConfiguration, WKPreferences or WKWebsiteDataStore (as ITP control storage policies).
Maciej Stachowiak
Let's assume ITP could end up on by default. It would be useful to hear from app developers who would want to turn it off if that happened. More specifically, why they want to do that, and how their app uses web views (is it general web browsing or some kind of content tied to the app?).
Ali Juma
(In reply to Maciej Stachowiak from comment #4)
> Let's assume ITP could end up on by default. It would be useful to hear from
> app developers who would want to turn it off if that happened. More
> specifically, why they want to do that, and how their app uses web views (is
> it general web browsing or some kind of content tied to the app?).
From the web browser standpoint, it'd be useful to give users the option to turn it off, for the same kinds of compatibility bugs for which Safari still offers users the option to turn it off. In other words, as long as there are sites that break with third-party cookies disabled, it'd be unfortunate if Safari has a workaround (disable ITP) but other browsers on iOS cannot offer this workaround.
Daniel Röder
(In reply to Maciej Stachowiak from comment #4)
> Let's assume ITP could end up on by default. It would be useful to hear from
> app developers who would want to turn it off if that happened. More
> specifically, why they want to do that, and how their app uses web views (is
> it general web browsing or some kind of content tied to the app?).
Such an Szenario is described here: https://bugs.webkit.org/show_bug.cgi?id=213879