More obvious steps to reproduce:
1. on iOS navigate to settings->Safari->Block Cookies, choose "Always Allow".
2. Navigate to https://usa.visa.com/pay-with-visa/visa-checkout.html (this website has good visual difference when 3rd party cookies are blocked or not).
actual.png -- when 3rd cookies are blocked
good.png -- when 3rd party cookies are allowed

Expected:
good.png

Actual:
actual.png

On Safari it changes depends on cookies settings. On Chrome is's always as actual.png.

I have no issues on iOS 9.3.5 on Any version of Chrome, so it seems it's not about Chrome version, but it's about webkit version. On this device webkit is 601.1.46

I always have issues (3rd party cookies are always blocked) on any OS, on any Chrome with Webkit 602.1.50 or higher.

mrefaat, it looks like external dependency?

Deleted: actual.png 117 KB

	actual.png 117 KB View Download

Deleted: good.png 273 KB

	good.png 273 KB View Download

Mohammad, please comment on this bug

I can't reproduce this on ios 11 - Chrome 64 & Chrome canary with cookies enabled.
I believe the website changed their mobile website - even when i block the cookies safari still the correct version appears in the website.
Will see if there is a way to test that on different website or will create a test case for it

The customer of case ID: 13957339 created a new case ID: 16450972 to ask for the current status of this issue. Can you please confirm if any feasible ETA on this issue soon ?

Eugene: what are next steps here? It doesn't appear we can repro this from our end (or at least we couldn't in January). 

I'd i believe this is not an issue any more (this is handled by the WKWebview and i wasn't able to reproduce anyway), we should close the bug.
If any new reports came we can at least get a website to be able to reproduce.

This issue is still reproducible on iOS
Chrome Version: 69.0.3497.105
iOS version:12
"Prevent cross-site tracking" disabled in Safari settings
Easy way to test - 
Visit whatismybrowser.com and check Third-party cookies section
Or https://en.support.wordpress.com/third-party-cookies/ and look under "Checking your browser..."

There seems to be no way to enable third-party cookies in Chrome, while they work in Safari at the same time.

Unfortunately we don't have a way to make third-party cookies work on Chrome. 
There is an outstanding webkit bug for that: 
https://bugs.webkit.org/show_bug.cgi?id=140205

WebKit bug is about blocking third party cookie. Unless I miss something, I think this bug is about setting 3rd party cookie. 

The bug is about being able to set the cookie policy in WKWebView, so that would cover multiple cases:

 Bug 140205 : WKWebView does not provide a way to set cookie accept policy
<https://bugs.webkit.org/show_bug.cgi?id=140205>

Agreeing with comment# 15,
 The default cookie accept policy seem to block third party cookies, i created a sample wkwebview to verify that. 
and when using    [pool performSelector:NSSelectorFromString(@"_setCookieAcceptPolicy:") withObject: NSHTTPCookieAcceptPolicyAlways];
It was able to accept third party cookies.

Interesting. Did we have "Allow 3rd party cookie" as default on iOS 11 and now "Block 3rd party cookie" is default on iOS 12?

Unfortunately a lot of web sites rely on 3rd party cookie to function, so having "Block" as default will break those sites.

may be at some point it was default but i'm testing on iOS 11.4 and it seem to have block as default.
and that's the case on all iOS browsers other than Safari 

Thanks mrefaat@ and eugenebut@.
Any way we can change the default behavior to allow (as mentioned in c#16)? Or, allow users to adjust it via a flag in the Chrome browser on iOS? 
As I understand, most modern browser will have third party cookie enabled by default for tracking and authentication purposes.

Unfortunately WKWebView does not provide public API to change cookie accept policy. And calling private API (like _setCookieAcceptPolicy:) is not allowed by AppStore guidelines.

My guess is that all iOS browsers (except Safari) do not allow 3rd party cookies on iOS 12. Safari have more control over cookie policy.

Apologies for the frequent ping but is there an update from WebKit's end on this issue? 
An enterprise customer of ours is asking for an update.

> Apologies for the frequent ping but is there an update from WebKit's end on this issue?
> An enterprise customer of ours is asking for an update.

Updates will be made in this bug, which is open to the public:
<https://bugs.webkit.org/show_bug.cgi?id=140205>

If the enterprise customer has their own contact within Apple's WWDR organization, they should file a radar via https://bugreport.apple.com/ and/or contact WWDR to let them know they are interested in this feature.  (Providing the bugs.webkit.org bug number in their radar and/or through contact with WWDR will make sure the correct issue is being discussed.)

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Thursday, 01/17/19 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

No one is actively working on this bug. The bug can not be fixed in Chrome. Why do we want to Archive the bug? ExternalDependency seems like more reasonable Status for a bug which requires WebKit changes.

Thanks for the update. This bug was selected as part of a process to close/resolve any bugs that aren't actively being worked on but have been left open. 

Since this is a P1 I was hoping to get some sort of update on if this is still actively being worked on. If this is no longer a P1 issue it may be best to lower the priority to something more appropriate.

Please let me know if you have any other questions or if there's anything I can do to help continue to make progress on this!

Thanks for the explanation. Removing milestone and lowering priority, since the bug can't be fixed for M-70 anyways.

Thanks again, eugenebut. Would you happen to know if there's any sort of ETA on when a fix can be expected?

Apple never comment on future releases, and it's unclear if fixing the bug is even a priority for them.