Reposition Preferences window after it has been made invisible

RESOLVED WONTFIX

Status

SeaMonkey
Preferences
RESOLVED WONTFIX
16 years ago
6 years ago

People

(Reporter: Charles Rosendahl, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [2012 Fall Equinox])

(Reporter)

Description

16 years ago
If a user has opened the preferences window, and then moves it but does not
close it, and then proceeds to use other app windows (browser windows, mail
client, editor, etc.), selecting to edit preferences from any of the open
windows does the correct thing:  It brings the preference window to the front in
focus in the last known position.

However, should the user dismiss the window, the last known position is
remembered when the window is reopened.  This is incorrect.  Upon dismissing the
window, the next time that the user opens the preferences, it should be
positioned relative to the window from which the preferences are opened.

Effectively, while it is still open, the user knows that it is open and uses it
relative to what the user is currently doing.  Once dismissed, the prior
interaction with the preference window is complete.  Once opened again, the
interaction is a new one, and not a continuation of the previous one.
Mass reassign of my non-Firefox bugs to ben_seamonkey@hotmail.com
Assignee: bugs → ben_seamonkey
Product: Browser → Seamonkey
Assignee: ben_seamonkey → prefs
QA Contact: bugzilla
(Filter "spam" on 'prefs-nobody-20080612'.)
Assignee: prefs → nobody
QA Contact: prefs

Comment 3

6 years ago
If user move Preferences window to some position then there was some reason for it and not saving it's position is bad idea here. Proposing WONTFIX
Whiteboard: [2012 Fall Equinox][CLOSEME 2012-11-01 WONT]

Comment 4

6 years ago
> Proposing WONTFIX
Yep
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX

Updated

6 years ago
Whiteboard: [2012 Fall Equinox][CLOSEME 2012-11-01 WONT] → [2012 Fall Equinox]
You need to log in before you can comment on or make changes to this bug.