WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
39278
Cookies not removed on Reset Safari
https://bugs.webkit.org/show_bug.cgi?id=39278
Summary
Cookies not removed on Reset Safari
Ain Tohvri
Reported
2010-05-18 02:49:33 PDT
This isn't a WebKit issue and is probably InRadar already, but: 1. Choose Safari > Reset Safari... 2. Check in all ticks 3. Reset 4. Go to Safari > Preferences > Security and click on Show cookies All cookies are still there and were not removed.
Attachments
Add attachment
proposed patch, testcase, etc.
Brady Eidson
Comment 1
2010-05-18 09:41:37 PDT
(In reply to
comment #0
)
> This isn't a WebKit issue and is probably InRadar already, but: > > 1. Choose Safari > Reset Safari... > 2. Check in all ticks > 3. Reset > 4. Go to Safari > Preferences > Security and click on Show cookies > > All cookies are still there and were not removed.
Safari 4.0.5 works. Running with nightly
r59633
this does appear to be busted.
John Sullivan
Comment 2
2010-05-18 09:52:20 PDT
Brady says he looked in the console and there was no output. He also says that he reproduced by just checking "Remove All Cookies" (didn't need to check everything else in the Reset dialog). I cannot reproduce with nearly-ToT Safari, on Leopard, with WebCore-59606. Maybe this was introduced after 59606, or maybe it doesn't occur on Leopard, or maybe it only occurs with nightly builds (which use released Safari, not ToT Safari).
Brady Eidson
Comment 3
2010-05-18 10:13:14 PDT
Actually, I can't reproduce this running nightly frameworks against Safari 4.0.5.
Brady Eidson
Comment 4
2010-05-18 10:13:36 PDT
<
rdar://problem/7997632
>
John Sullivan
Comment 5
2010-05-18 10:53:11 PDT
We could reproduce a bug with these symptoms in Safari, but it was a problem in tip of tree Safari and is not reproducible running tip of tree WebKit with a released version of Safari. So there's something of a puzzle here as to what version of Safari was being used by the submitter. In any case, this is a Safari-level issue, so changing status to Resolved/Invalid. The issue is now being tracked in radar.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug