Closed
Bug 295368
Opened 20 years ago
Closed 17 years ago
Cookie still set when button 'Deny' is clicked
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: Lifesgraces, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 A cookie is still set even if the button 'Deny' is clicked. Reproducible: Always Steps to Reproduce: 1. Wait for a Cookie window to appear with the buttons for allowing or denying it. 2. Click 'Deny' 3. Take a look at the stored cookies in the Cookie Manager Side-Note -- if in fact this is random or semi-random intermittent behavior rather than every single time, then take a look at the stored cookies after every single time you click the botton 'Deny' (or in the case of a page that sets multiple cookies one after another, then wait to look until after all cookie window/prompts have been answered, making note of the name of each cookie as it is prompted for so as to know their names when you look in Cookie Manager). Actual Results: Click on 'Deny' but the cookies are still being accepted and displayed in Cookie Manager. Expected Results: No cookie set. It's slightly possible that this isn't happening every single time, but it is at least happening enough to be a bug -- I click on Deny, cookies are accepted anyway. With sites that are permanently marked as "Cannot Set Cookies," there is no problem.
Could you please test it with Mozilla 1.7.8?
Version: unspecified → 1.7 Branch
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 I am using one day and it nothing show in Manager Cookies. Kirby, is this still a valid bug?
Comment 3•17 years ago
|
||
(2.5+ years later) No reply from reporter. MozillaAS v1.7.x is not supported anymore. (Would have been "Incomplete", now is) R.Invalid Reopen if you can reproduce with SeaMonkey v1.1.9.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•