Open
Bug 330861
Opened 19 years ago
Updated 2 years ago
by default (content)window.moveTo should do nothing or at least not unmaximize a window
Categories
(Core :: DOM: Core & HTML, enhancement, P5)
Tracking
()
NEW
People
(Reporter: timeless, Unassigned)
Details
If I'm a user, and I maximize a window, and i start browsing, I expect that my window will remain maximized. Now, there is a Advanced>Scripts & Plugins>Allow scripts to: Move or resize existing windows pref, but there's a difference between me wanting to allow scripts to move normal windows, and not wanting a maximized (or minimized) window to be restored. Note: this is limited to web content. Presumably if chrome wants to minimize, restore, or maximize a window, it has a good reason.
Comment 1•19 years ago
|
||
I disagree with your assertion that maximized windows are special and web content shouldn't be able to resize them. Why is it ok with you for web sites to screw with your un-maximized windows but not with your maximized windows? I recommend WONTFIX (for making the maximized state special) or DUP of bug 186708. See also bug 111545, "script that tries to 'almost maximize' an already-maximized window unmaximizes it".
Updated•15 years ago
|
Assignee: general → nobody
QA Contact: ian → general
Comment 2•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•