Window moves when mouse is not down (Mozilla thinks drag is enabled when it's not)



15 years ago
12 years ago


(Reporter: Kevin Ar18, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030706 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030706 Mozilla Firebird/0.6

When you launch a new browser window, it takes some processing time for the
window to get drawn (not referring to rendering a page, but simply drawing the
window).  If you click on the title bar, drag, and let go of the mouse before
the window has rendered itself, then after it is done rendering Mozilla things
drag is still enabled and thus, the window follows the cursor around the screen
as you move your mouse even though you have no button pressed.

Reproducible: Always

Steps to Reproduce:
I suppose you could reproduce this bug using any link, but sometimes windows
just load/render faster than others and it makes it harder to catch this bug.
I will thus direct you to where I first caught on to the issue:
1. See the following link?
2. Right click on it and select "Open in New Window"
3. In order to catch the problem you must be quick.  Before the window has
rendered itself (aka the scrollbar will be missing, however, the toolbar and
menubars will be present) do the following:
A. click on the title bar (like you are going to move the window)
B. Drag your mouse anywhere very quickly
C. and release the button before the window had a chance to render.
Actual Results:  
1. You will notice that the Window did not move before it was done rendering
(before you saw the scrollbar).
2. After the window actually renders, you will notice that as you move your
mouse, the window moves with it (even though you have no buttons pressed).

Expected Results:  
1. The Window should have moved even before it was done rendering - after all,
you did click and drag the window somewhere. -- IE works in this manner.
2. After it was done rendering, the window should not have moved - because you
did not have your mouse button pressed down.

Note: This bug occurs whether you use the Windows XP default (luna) scheme or
whether you use the classic scheme.  (I'll need someone to check if it's a cross
platform issue.)  This bug occurs in Mozilla with default theme as well as
Mozilla Firebird with custom theme.

Comment 1

14 years ago
Unable to reproduce with 1.7 alpha or nightly build 2004022909 on windows XP
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME

Comment 2

14 years ago
I have encountered this bug on a different system.
OS: Windows 98
Firefox 0.9

The bug occurred on a window generated by javascript.  As described in the first
comment, I clicked on the title bar before the window itself had finished rendering.

I do not know a way to make the system slow enough so that it will always create
a window that takes a few seconds to render.  However, the only trick to being
able to reproduce this bug is to click and drag the title bar before the actual
window (not the page contents) has rendered; the window is blank white before it
begins to render.

I will have to test further to see if this is OS related or browser related.
Resolution: WORKSFORME → ---
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 14 years ago12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.