Closed
Bug 168585
Opened 23 years ago
Closed 23 years ago
Password and cookie managers reverses order when removing entries
Categories
(SeaMonkey :: Passwords & Permissions, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.2beta
People
(Reporter: kylem+bugzilla-mozilla, Assigned: morse)
References
Details
(Keywords: regression)
Attachments
(1 file, 1 obsolete file)
|
2.39 KB,
patch
|
samir_bugzilla
:
review+
jag+mozilla
:
superreview+
|
Details | Diff | Splinter Review |
Running 1.2-alpha (2002091014). In Password Manager, when the list is sorted by
Site, removing any username/password line causes the list order to be reversed.
This includes going back and forth if removing one password after another.
| Assignee | ||
Comment 1•23 years ago
|
||
Same problem occurs for cookie manager. This is a regression that was
introduced when the cookie manager dialog and password manager dialog were made
to dynamically update.
Confirming and accepting.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Keywords: nsbeta1,
regression
Priority: -- → P2
Summary: Password manager reverses order when removing password → Password and cookie managers reverses order when removing entries
Target Milestone: --- → mozilla1.2beta
| Assignee | ||
Comment 2•23 years ago
|
||
| Assignee | ||
Comment 3•23 years ago
|
||
Attachment #99930 -
Attachment is obsolete: true
Comment 4•23 years ago
|
||
Comment on attachment 100005 [details] [diff] [review]
make correction only if last sort column was the host column
r=sgehani
Attachment #100005 -
Flags: review+
Comment 5•23 years ago
|
||
Comment on attachment 100005 [details] [diff] [review]
make correction only if last sort column was the host column
sr=jag
Attachment #100005 -
Flags: superreview+
| Assignee | ||
Comment 6•23 years ago
|
||
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 7•23 years ago
|
||
*** Bug 171097 has been marked as a duplicate of this bug. ***
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•