Firefox version of bug 124750. I'm filing this so I can set the blocking 1.0 flag, because this is one of my biggest usability beefs with ff right now.
15 years ago
Assignee: bugs → bryner
15 years ago
Priority: -- → P3
Target Milestone: --- → Firefox1.0beta
*** Bug 249441 has been marked as a duplicate of this bug. ***
*** Bug 250242 has been marked as a duplicate of this bug. ***
I would raise the severity to major
As was mentioned in comment #146 over at the sister-bug 124750 I'd suggest rising the severity to Critical based on the information from http://www.mozilla.org/security/bug-bounty-faq.html#critical-bugs "What types of security bugs do you consider to be "critical"? [...] that otherwise allow access to users' confidential information. In the latter case we consider bugs to be critical only if they potentially expose high-value personal information (e.g., passwords, credit card numbers, and the like); [...]" Just thought I'd add it here as well as it's a good suggestion and I suspect not everyone is monitoring that bug. See the comment in question for further information.
Severity should mirror that of Bug 124750 -- currently 'major'
setting severity to major (to match browser bug) also, all/all
Severity: normal → major
Hardware: PC → All
*** Bug 256552 has been marked as a duplicate of this bug. ***
okey stop blocking this bug for the 1.0 release 'cause it wont be fixed before the final... What went wrong with the planification for this password-revealing bug ? That kind of bug should have the team focused on it at a set date and work it out or something.
(In reply to comment #8) > okey stop blocking this bug for the 1.0 release 'cause it wont be fixed before > the final... > > What went wrong with the planification for this password-revealing bug ? That > kind of bug should have the team focused on it at a set date and work it out or > something. Removing security and/or usability bugs (with 30+ votes, none-the-less) from the 1.0 'blocker' list to hurry the release out the door is a *very* bad idea. That said... Bugzilla is not a forum. Please take your topic of discussion to www.mozillazine.org
heu, it's not a request, it's an affirmation. This bug is irritating me and certainly didn't want to see this bug still hanging around with 1.0 final. from bug 124750 ------- Additional Comment #156 From Brendan Eich 2004-09-13 11:49 PDT [reply] ------- Comment 155 is insulting noise. This bug won't get fixed without significant Gecko focus re architecture, which has not and will not fit into the aviary branch before 1.0. We will fix it after 1.0, as soon as is practical. /be
*** Bug 259264 has been marked as a duplicate of this bug. ***
*** Bug 259268 has been marked as a duplicate of this bug. ***
*** Bug 259279 has been marked as a duplicate of this bug. ***
I may have talked jst into attempting a dom&docshell hackaround.... /be
Not a "blocker"
Flags: blocking-aviary1.0+ → blocking-aviary1.0-
Coincidentally, bug 124750 was just fixed on the aviary branch. (I think this definitely should have been a blocker, but that's irrelevant now.) In fact, I've lost track of why I filed this bug. Perhaps at one time 124750 didn't have a blocking-aviary1.0 flag...? Regardless, it does now and this is definitely a dupe of that bug. *** This bug has been marked as a duplicate of 124750 ***
Status: NEW → RESOLVED
Last Resolved: 14 years ago
No longer depends on: 124750
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.