Closed
Bug 125231
Opened 23 years ago
Closed 15 years ago
Password/Form/Cookie/Image Managers have incorrect title bar menus
Categories
(SeaMonkey :: Passwords & Permissions, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
Future
People
(Reporter: dc2, Unassigned)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.8+) Gecko/20020212
BuildID: 2002021203
Similar to bug 101851. The four managers available from the Task > Privacy &
Security have title bar menu options selectable when they should be greyed out.
Reproducible: Always
Steps to Reproduce:
1. Choose e.g. Password Manager > Manage Stored Passwords.
2. Right-click on title bar menu.
Actual Results: Restore/Minimise/Maximise are selectable.
Expected Results: I'm not entirely sure if the dialog box should be resizable
(it's modal). If it is then it should be a normal menu but with
Restore/Minimise/Maximise greyed out. If not then only Move and Close should be
on the menu.
The same happens with the other three managers.
Does something similar happen on Win 2000/XP, MacOS, Linux?
Comment 1•23 years ago
|
||
Does not happen for me, same build WinXP
Something similar happened in bug 101851 (problem for Win 9x, no problem for Win
2000/XP).
Confirming on 2002021403, Win98 and marking as new. Imo, the
Password/Form/Cookie/Image Managers must be resizable so only Minimize must be
disabled. It doesn't seem to be a general problem with all modal dialogs (Find
is ok).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•23 years ago
|
||
Is this bug still valid?
The managers seem to have been changed to non-modal (at least that is what I see
on 2002071108 and is mentioned in initial report of bug 156922).
So the title bar menus show the right things IMO.
Only "Form Manager"-"Manage Sites" is still not resizable (bug 139188), but its
title bar also shows the correct choice (as do the find and preferences dialogs).
uid is being phased out.
Assignee: mpt → morse
Component: User Interface Design → Password Manager
QA Contact: zach → tpreston
Updated•23 years ago
|
Target Milestone: --- → Future
Reassigning to new module owner.
Assignee: morse → dveditz
see bug 101851
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: dveditz → nobody
Updated•17 years ago
|
QA Contact: tpreston
![]() |
||
Comment 8•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
![]() |
||
Comment 9•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•