User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Hey there all Firefox users! if you keep up with the times, you now have a gaping security hole in your system, why, don't know, but according to email@example.com: "Just because a feature exists at some point does not mean we are under any obligation to you or anyone to continue to support that feature." See Bug 264297 if it has not been censored from the system Firefox *used* (since as far back as I remember) have a provision to allow you to allow all cookies/BUT ASK FIRST. For no sane reason, this was hacked out of the code. Apoparently taking them to task for allowing al of us to be cookie-raped is, firstname.lastname@example.org says a "bogus issue" New Version allows user to allow any and all cookies, then, after a session of doubleclicks, et. al. decide whether s/he wishes to allow those cookies to remain on the system. HOW NICE. Yeh, I was rude - 'cause I cannot cut code, and have NO WAY of undoing the damage you did for NO REASON to a fine program/feature. It is a security hole 10 feet wide and should be closed ASAP! Reproducible: Always Steps to Reproduce: 1.install current version of Firefox 2.Expect that basic security features being transferred include basic security features there since Phoenix days 3.Find yourself with 120 unwanted cookies, tracing you all over the place Actual Results: Old cookie system: Accept All Cookies, but ASK FIRST New one: Accept all cookies and ask after the fact Expected Results: Been left unchanged! Instead, send angry user a note reading in part:"Just because a feature exists at some point does not mean we are under any obligation to you or anyone to continue to support that feature" instead of restoring the code. Reads like the Gates letter about "stealing" the version of BASIC ha stole himself - neet - huh? How many users have now been dblclicked by this unannounced new "improvement"
Just as a note: I was assuming the reporter actually read the comment before mine which told him exactly how to get his desired behaviour. I was simply pointing out that being rude and demanding had no place in this project. Perhaps in greater detail than was needed, but I tend to respond in kind. Next time, try reading first, then responding. Filing bogus bugs is just a quick way of getting a Bugzilla account terminated. Just to recap, again, under Keep Cookies choose "Ask me every time" and the feature you've ranted at length about us removing is magically still there.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → INVALID
Summary: Security hole excavated, then ignored by QA McConnor (see bug 264297 if not stripped from the list) → user can't find the option to turn on cookie prompts
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in before you can comment on or make changes to this bug.