Closed
Bug 150628
Opened 23 years ago
Closed 23 years ago
image/cookie manager doesn't remember window position
Categories
(Core :: Networking: Cookies, defect, P4)
Tracking
()
VERIFIED
DUPLICATE
of bug 170172
mozilla1.3beta
People
(Reporter: mozilla, Assigned: morse)
References
Details
image manager doesn't window position, column widths
same with cookie one
Comment 1•23 years ago
|
||
-> Image Blocking
Assignee: Matti → morse
Component: Browser-General → Image Blocking
QA Contact: imajes-qa → tever
Comment 2•23 years ago
|
||
Read this, please. http://www.mozilla.org/quality/bug-writing-guidelines.html
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Hrm, somehow some words got lost from the desc. Here it is again:
Applies to image manager and cookie manager
1) window position always opens on (0,0)
2) column widths always default.
Now, normally you expect a window to 1) remember last position, or ,2) open
center screen
Additional 'issues':
You can open more than one! Since it's a global setting, this isn't so good.
It doesn't refresh when you add/rem stuff via browser. <- not so critical
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Summary: image manager doesn't window position → image manager doesn't remember window position
Comment 4•23 years ago
|
||
Confirming that image managers always open top left on Mozilla/5.0 (Windows; U;
Win98; en-US; rv:1.2b) Gecko/20021002.
For additional problems please open new bugs.
pi
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Component: Image Blocking → Cookies
Priority: -- → P4
Summary: image manager doesn't remember window position → image/cookie manager doesn't remember window position
Target Milestone: --- → mozilla1.3beta
Updated•23 years ago
|
Blocks: RememberPosition
Assignee | ||
Comment 5•23 years ago
|
||
*** This bug has been marked as a duplicate of 170172 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•