-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Update platform guards and add notImplemented() call in shouldTreatAsSameSite #44751
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…SameSite https://bugs.webkit.org/show_bug.cgi?id=292334 Reviewed by NOBODY (OOPS!). We can use the new implementation on any platform that implements the cookie change listener API. Add a notImplemented() warning everywhere else. * Source/WebKit/NetworkProcess/NetworkConnectionToWebProcess.cpp: (WebKit::shouldTreatAsSameSite):
EWS run on current version of this PR (hash e07a2d9) |
I'm no longer a maintainer of the ports. I hope the right person reviews this. I don't know who. |
Ping reviewers |
1 similar comment
Ping reviewers |
@@ -781,12 +781,14 @@ void NetworkConnectionToWebProcess::registerURLSchemesAsCORSEnabled(Vector<Strin | |||
|
|||
static bool shouldTreatAsSameSite(const URL& firstParty, const URL& url) | |||
{ | |||
#if PLATFORM(COCOA) || USE(SOUP) | |||
#if HAVE(COOKIE_CHANGE_LISTENER_API) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using COOKIE_CHANGE_LISTENER_API
here is super confusing to me as I don't see what this has to do with cookie changes listening. Can you clarify why we need a compile guard at all? The code below doesn't looks COCOA / SOUP specific at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All I know is it "breaks tests," see: https://bugs.webkit.org/show_bug.cgi?id=285969#c2
We were able to add the || USE(SOUP)
condition after implementing cookie change listener API in https://commits.webkit.org/289693@main so it's definitely tied to that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could try removing the guards and see what breaks on Windows EWS. (But this will go onto my to-do list rather than for today.)
e07a2d9
e07a2d9