Bug 205963 - Resource Load Statistics: Flip experimental cookie blocking setting from an enable to a disable
Summary: Resource Load Statistics: Flip experimental cookie blocking setting from an e...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Misc. (show other bugs)
Version: WebKit Local Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: John Wilander
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2020-01-08 15:28 PST by John Wilander
Modified: 2020-01-08 17:21 PST (History)
3 users (show)

See Also:


Attachments
Patch (10.40 KB, patch)
2020-01-08 15:46 PST, John Wilander
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description John Wilander 2020-01-08 15:28:09 PST
To get default on behavior, experimental features in the network process need to be turned from enable to disable flags. We should do that for the experimental cookie blocking setting.
Comment 1 Radar WebKit Bug Importer 2020-01-08 15:28:35 PST
<rdar://problem/58424136>
Comment 2 John Wilander 2020-01-08 15:46:14 PST
Created attachment 387149 [details]
Patch
Comment 3 Brent Fulgham 2020-01-08 16:03:47 PST
Comment on attachment 387149 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=387149&action=review

> Source/WebKit/UIProcess/WebsiteData/Cocoa/WebsiteDataStoreCocoa.mm:75
> +    auto thirdPartyCookieBlockingMode = WebCore::ThirdPartyCookieBlockingMode::All;

When would we ever hit 'OnlyAccordingToPerDomainPolicy'?
Comment 4 John Wilander 2020-01-08 16:11:35 PST
(In reply to Brent Fulgham from comment #3)
> Comment on attachment 387149 [details]
> Patch
> 
> View in context:
> https://bugs.webkit.org/attachment.cgi?id=387149&action=review
> 
> > Source/WebKit/UIProcess/WebsiteData/Cocoa/WebsiteDataStoreCocoa.mm:75
> > +    auto thirdPartyCookieBlockingMode = WebCore::ThirdPartyCookieBlockingMode::All;
> 
> When would we ever hit 'OnlyAccordingToPerDomainPolicy'?

It was the old default but now it's only needed to be able to run layout tests with non-ITP behavior by default. The TestRunner falls back to this old setting for all tests that don't explicitly test ITP's behavior. Otherwise a bunch of tests that assume cookie access would not pass.

My reasoning is that since users can turn off ITP and WKWebViews don't run with ITP, the rest of the layout test suite needs to continue testing under such conditions.

(Per-domain policy effectively means that if the layout test doesn't make a domain prevalent, ITP won't do anything, ergo non-ITP behavior.)

I hope this makes sense.

Thanks for the review!
Comment 5 WebKit Commit Bot 2020-01-08 17:21:09 PST
Comment on attachment 387149 [details]
Patch

Clearing flags on attachment: 387149

Committed r254239: <https://trac.webkit.org/changeset/254239>
Comment 6 WebKit Commit Bot 2020-01-08 17:21:10 PST
All reviewed patches have been landed.  Closing bug.