Closed
Bug 19188
Opened 25 years ago
Closed 24 years ago
Should be able to move windows off top of screen
Categories
(Core :: XUL, defect, P4)
Tracking
()
VERIFIED
FIXED
Future
People
(Reporter: sfraser_bugs, Assigned: danm.moz)
References
Details
We currently have some code that prevents you from dragging windows so that their
titlebars are above the top of the screen. If you try to drag the window up, it
snaps back down again.
I know of no other application that has this behaviour, so I don't think we
should do it. We do need to ensure that the whole window cannot be moved
offscreen, but we should not impose this 'title bar must be visible' restriction.
Have you tried this an another app. Codewarrior, 4.7, and sherlock all do this
leading me to think this might be an apple thing
Reporter | ||
Comment 2•25 years ago
|
||
Codewarrior only does that if the toolbar is showing. 4.5 doesn't do it for me.
Sherlock doesn't count ;)
Whats the test case here. What I am doing is dragging the window and when the
cursor hits the menu bar the drag aborts. Happens to me in every app. Sounds
like a XPToolkit problem anyway;)
Reporter | ||
Comment 4•25 years ago
|
||
Ah, I should have been more clear. I'm dragging the window by clicking the window
border around the sides, or bottom.
Assignee: davidm → trudelle
Component: Browser-General → XP Toolkit/Widgets
There is code in the nsWindowMac which prevents having part of the window off
the top of the screen. reassign to XPToolkit as I think they own this code.
Updated•25 years ago
|
Assignee: trudelle → danm
Priority: P3 → P4
Target Milestone: M18
Comment 6•25 years ago
|
||
assigning to danm as p4 for m18
Comment 7•25 years ago
|
||
Note the comments in nsMacWindow.cpp, line 606:
// move the window if it has not been moved yet
// (ie. if this function isn't called in response to a DragWindow event)
It means that something is broken. If the function is called in response to a
DragWindow, we should not make the window snap back down on the screen. I put
this code so that the application can't by mistake display or move a window out
of the screen bounds. The case may happen for instance when moving a user profile
from a machine with a large screen to a machine with a smaller one.
On a related note: before moving to CSS, I wanted to re-arrange the way the
DragWindow/SizeWindow events were processed. If you (pink? saari?) want to know
more, we can discuss about it.
Comment 10•25 years ago
|
||
mass-moving all bugs to m21 that are not dogfood+ or nsbeta2+ or nsbeta2-
Target Milestone: M19 → M21
Assignee | ||
Comment 11•25 years ago
|
||
moving en masse all bugs that didn't get nsbeta3 nomination to "future" milestone
Target Milestone: M21 → Future
Comment 12•24 years ago
|
||
I believe this has been fixed. Windows can be moved anywhere on (or off) screen.
Assignee | ||
Comment 13•24 years ago
|
||
Quite right; this was fixed as a side effect of the fix for bug 31516.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 14•24 years ago
|
||
marking VERIFIED Fixed. With a 2001032804 Mac build(OS 8.5.1) I can grab a window by the
bottom or sides and drag it such that the title bar of the window is offscreen without incident.
Status: RESOLVED → VERIFIED
QA Contact: claudius → jrgm
Comment 15•19 years ago
|
||
*** Bug 321214 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•