Closed Bug 87764 Opened 24 years ago Closed 3 years ago

Magic scrollbars: leaving browser window boundary causes thumb to follow mouse

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE
Future

People

(Reporter: masri, Unassigned)

References

()

Details

Platform: PowerBook G3/300/192Mb/25Gb, MacOS 10.0.4. Fizzilla Build ID: 2001061314 Skin: Modern (whether it does this in Classic, I don't know. Since I've seen certain bugs that don't occur until switching from the Classic skin, it is possible that my browser prefs are "tainted" by Modern skin, in which case any testing by me would be worthless.) I have been seeing the following bug for months, and I've finally figured out a reasonably reproducible set of steps to get it to do this. I hope you can too! You may have to follow steps 5-11 many times to finally get your Moz to do magic! Note that my screen is 1024x768; whether this is important, I don't know. But if you can't reproduce it, you may wish to set up your Mac to be as much like mine as possible. This bug is reproducible whether other software is running or not. 1) Open a single Moz window to approx. 1/2" away from edge of your dock, and perhaps 1" or so from the bottom of your screen. Window width should be approx. 3/4 of screen. 2) Set your homepage to my.netscape.com. 3) Make a decently complex (3 column) my.netscape page. This bug seems to be easier to generate the longer it takes Moz to build the page. A slower machine helps too. 4) Quit Netscape. Relaunch, so we all know we're in the same place. 5) Holding the mouse button on the scrollbar thumb, scroll the scrollbar thumb to the middle of the window, then down to CLOSE to the bottom. Let go of mouse button. 6) Move the mouse to the lower half of the scroll thumb. 7) Holding the mouse button on the lower half of the scrollbar thumb, drag the mouse down vertically towards the bottom of the screen, PAST the boundary of the Mozilla window (towards your dock). 8) Let go of the mouse button when you're outside the bounds of the Moz window. 9) Move the mouse anywhere within the scrollbar thumb. This is where you have to be fast. This needs to be as fluid as possible. If you screw up, you can go back to step 5 and continue from there. You may have to do this series of steps 5-10 times to see magic. (I can now do this probably 1 in 7 tries on average.) 10) Hold down on the mouse button over the scrollbar thumb. As fast as you can, drag up towards the menu bar, PAST the boundary of the Moz window. Do not let go of the mouse button until you're outside the bounds of the Moz window (towards the menu bar). 11) Without clicking the mouse button, immediately move the mouse diagonally and to the left, back WITHIN the bounds of the Mozilla window. Move your mouse vertically, NEVER entering the scrollbar region or leaving the bounds of the Moz window. See the scroll thumb? It's magically following your every move! Hear the crowd ooh and aaah... I do not have a repeatable set of steps, but I have seen this on the horizontal scrollbar as well. So when you're in there, please check on that too. And now for my next trick... - Adam
IIRC, I have seen this not only on Mac OS X but on Classic and Solaris, too.
If you follow these exact steps, can you duplicate on Solaris? I have a feeling that this bug is xp. I hope someone will chime in on Windows. - Adam
Not OS X specific
OS: MacOS X → All
Hardware: Macintosh → All
Target Milestone: --- → mozilla1.0
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
QA Contact: madhur → rakeshmishra
QA Contact: rakeshmishra → trix
.
Assignee: joki → saari
QA Contact: trix → ian
retargeting
Target Milestone: mozilla1.0.1 → Future
Assignee: saari → nobody
QA Contact: ian → events
Component: Event Handling → User events and focus handling

Page no longer active

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.