263727 - The scroll handle of select inputs from within a draggable DIV or LI drags the whole window..

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Emil Tamas]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041006 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041006 Firefox/0.10.1

See the attachment. This works OK in Mozilla suite.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Emil Tamas]

Attachment: the problem ..

Comment 2

[Martijn Wargers (dead)]

Do you have an URL or a testcase in which we can see the problem? Else, this bug
is pretty much unsolvable.

Comment 3

[Emil Tamas]

Here is a temporary link. (it's an app I'm working at)
http://emil.mynetrealty.com/vtour/index.php
Login as test/test, then choose post tour. then add new scene. On the new "scene
window" try to select the scene name by dragging the scroll handle.
Greetz, 
Emil Tamas

Comment 4

[José Jeria]

This worksforme, I see that  you have different linux looking scrollbars though
you are on Windows XP. Are you using a different theme? Does this happend with
the default theme?

Comment 5

[Emil Tamas]

I'm using a different Windows theme (not another FX theme). Anyway, I switched
to the classic theme, same effect. 

Comment 6

[Sitov Cristian]

Did saw it in action!!! My opinion is that as long as the "generated" scrollbar
is  the "child" of the <select> tag, the mouse actions should not affect the
scrollbar's behaviour, not even the <select> tag's parent should not change
their behaviour!!! On the other hand... while clicking somewhere between the
scrollbar and it's heads everything is normal!!! In conclusion, dragging the bar
the parent DIV will be affected (having the presumption that this DIV is
draggable)!!!

Comment 7

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 8

[Gervase Markham [:gerv]]

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.