RESOLVED CONFIGURATION CHANGED 19658
Safari 4 Developer Preview - setting document.cookie isn't working
https://bugs.webkit.org/show_bug.cgi?id=19658
Summary Safari 4 Developer Preview - setting document.cookie isn't working
Robbie Paplin
Reported 2008-06-18 11:49:19 PDT
The attached page has Javascript code to detect if cookies are enabled. The page will set a cookie, and then immediately try to read that cookie value. It appears that the cookie value isn't getting set by the script.
Attachments
Javascript Cookie Detection Test (1.33 KB, text/html)
2008-06-18 11:51 PDT, Robbie Paplin
no flags
Robbie Paplin
Comment 1 2008-06-18 11:51:35 PDT
Created attachment 21821 [details] Javascript Cookie Detection Test
Robbie Paplin
Comment 2 2008-06-18 11:52:21 PDT
Comment on attachment 21821 [details] Javascript Cookie Detection Test Change mime type to html
Robbie Paplin
Comment 3 2008-06-18 12:08:29 PDT
1. You need to empty your cookie cache before navigating to the test page in order to get the expected results. 2. The bug doesn't seem to repro consistently. When I ran this page from the local file system, it seems to repro. When I ran it from https://bugs.webkit.org, it doesn't seem to happen.
Ahmad Saleem
Comment 4 2022-08-11 04:34:05 PDT
I get following results in all browsers: All browsers were in "Private / Incognito" mode. *** Safari 15.6 on macOS 12.5 *** Actual Results: Cookies are enabled Cookie Value: cookieTest=1 *** Firefox Nightly 105 *** Actual Results: Cookies are enabled Cookie Value: cookieTest=1 *** Chrome Canary 106 *** Actual Results: Cookies are enabled Cookie Value: cookieTest=1 ___ Although - Safari do fail following test (Cross-site iframe cannot set lax/strict cookies via document.cookie): https://wpt.fyi/results/cookies/samesite/iframe.document.https.html?label=master&label=experimental&aligned&view=subtest&q=document%20cookies Appreciate if someone can mark this bug accordingly. Thanks!
Ryosuke Niwa
Comment 5 2022-08-11 12:27:31 PDT
This seems config changed to me.
Note You need to log in before you can comment on or make changes to this bug.