[Webkit-unassigned] [Bug 137745] When in private mode, cookies in iFramed content are not set correctly
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Oct 30 17:06:36 PDT 2014
https://bugs.webkit.org/show_bug.cgi?id=137745
--- Comment #4 from Alexey Proskuryakov <ap at webkit.org> ---
What is your cookie accept policy in Safari? With the default policy, a cross-origin subframe is not allowed to store cookies.
I suspect that you have a non-default policy set in Safari preferences, and that using private browsing reverts that to default. If so, Safari/WebKit behavior seems incorrect, but I'd like to confirm that this is indeed what you are seeing.
> * If you right click the iframe, and select "Open Frame in New Tab", the page will load and render the correct value. Bizarrely, if you then go back to http://run.plnkr.co/my0lgusP2UEYNTbL/ and refresh the page, the iframe will load with the correct value!
Yes, this is expected for the default cookie policy - cross-origin subframes may not store cookies, but they can read existing ones.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20141031/a6279989/attachment-0002.html>
More information about the webkit-unassigned
mailing list