Closed Bug 551934 Opened 15 years ago Closed 14 years ago

When switching between tabs, scrollbars become unable to be dragged.

Categories

(Firefox :: General, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: question2005, Unassigned)

Details

(Whiteboard: [CLOSEME 2011-1-30])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) Referring to the scrollbars to the right/bottom of a web page. I have noticed that when switching between tabs, sometimes the scrollbars get stuck and cant be moved if i click->hold down mouse 1->drag them. I can still click on an empty spot in the scroll bar to move the scroll bar, but i cannot drag the scrollbar. The scrollbar becomes undrageable. It seems to be fixed most of the time if i refresh the page, but it occurs frequently for me when i switch between tabs. Reproducible: Sometimes Steps to Reproduce: 1.Switch between tabs 2.??? 3.PROFIT! Actual Results: Most of the time if i switch between tabs often enough, the scrollbar of some of the tabs will get stuck and become undrageable. It should have allowed me to drag the scrollbars.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
Given the fact that the bug was reproted 9 months earlier and we are alraedy in firefox 4 beta 8, what do you think? I am not going to bother reporting bugs here again.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.