39278 2010-05-18 02:49:33 -0700 Cookies not removed on Reset Safari 2010-05-18 10:53:11 -0700 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) Mac (Intel) OS X 10.6 RESOLVED INVALID InRadar P2 Normal --- 0 ain webkit-unassigned ap beidson sullivan oldest_to_newest 227210 0 ain 2010-05-18 02:49:33 -0700 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. 227352 1 beidson 2010-05-18 09:41:37 -0700 (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. 227356 2 sullivan 2010-05-18 09:52:20 -0700 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). 227361 3 beidson 2010-05-18 10:13:14 -0700 Actually, I can't reproduce this running nightly frameworks against Safari 4.0.5. 227362 4 beidson 2010-05-18 10:13:36 -0700 <rdar://problem/7997632> 227381 5 sullivan 2010-05-18 10:53:11 -0700 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.