MacOSX: Vertical scrollbar sometimes sticks when in top-most position

NEW
Unassigned

Status

()

--
major
13 years ago
8 years ago

People

(Reporter: mcafee, Unassigned)

Tracking

1.5.0.x Branch
PowerPC
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

13 years ago
Firefox 1.5.0.2
osx 10.4.6
ppc g5

This is a weird scrolling bug.  Some pages have a "sticky vertical
scrollbar" if the scrollbar gets to the top-most position.
I saw this happen just now on www.cartalk.com, and can reproduce
after restarting Firefox.  This doesn't seem to be a function
of tabs, and I don't see any obvious JS errors.

I can also reproduce this on a ! bugzilla list, make the
window smaller, move the vertical scrollbar to the top,
let go, then try to scroll down.  The behavior I am seeing
is that I can't drag the scrollbar down, I have to "page" it
down or use arrows to get it out of the top position,
then it starts working.
(Reporter)

Updated

13 years ago
Severity: enhancement → major

Updated

13 years ago
OS: Mac OS X 10.2 → Mac OS X 10.4

Comment 1

13 years ago
I think FF on Mac treats "Z-Index" and "visibility" poorly - specifically it forgets to actually apply the z-index or visibility to the scrollbars.  But by using style.display = 'none' and style.display = '', you can make the scrollbars disappear properly

Comment 2

12 years ago
The scroll bar slider gets stuck at the bottom of the scroll lane forcing the use of the up selector to unstick.  This is not intermitent; but, consistent whenever I reach the lower limit.  The Firefox version is 2.0.0.4 and the MacOS is 10.4.10 (the problem was also present in earlier versions of MacOS 10.4).  The system is a dual 800 MHz PowerPC G4 Quicksilver w/ a dual 1.73 GHz PowerPC G4 7448 upgrade (the problem was also present before the upgrade).
This bug is part of a query for Firefox bugs that have Status set to NEW, but have version field set to 2.0 or older and have not changed in over 800 days.

http://tiny.cc/forgottennewbugs

If you still see this bug, or if it is still valid with Firefox 3.6.10 or a firefox 4 nightly build, please update the version field and steps to reproduce.
You need to log in before you can comment on or make changes to this bug.