Bug 39278
| Summary: | Cookies not removed on Reset Safari | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ain Tohvri <ain> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ap, beidson, sullivan |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac (Intel) | ||
| OS: | OS X 10.6 | ||
Ain Tohvri
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
(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
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
Actually, I can't reproduce this running nightly frameworks against Safari 4.0.5.
Brady Eidson
<rdar://problem/7997632>
John Sullivan
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.