Scrolling with mouse wheel does not work, when mouse pointer is over certain parts of the table

RESOLVED WORKSFORME

Status

()

Firefox
General
RESOLVED WORKSFORME
11 years ago
11 years ago

People

(Reporter: ACHeron, Unassigned)

Tracking

2.0 Branch
x86
All
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.8.1.3) Gecko/20070525 Firefox/2.0.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.8.1.3) Gecko/20070525 Firefox/2.0.0.3

On some web pages the scrolling stops working, when mouse pointer comes over certain parts of the table. In the given example the problem area is the lower part of the left (green) column of all pages of the opensuse.org wiki, under the text. 

Distribution: Gentoo.

Reproducible: Always

Steps to Reproduce:
1. Go to http://en.opensuse.org/Documentation 
2. Put mouse pointer over the leftmost vertical green bar under the text. Try moving the wheel.
3. Put mouse pointer over the text on the green bar or outside the green bar.  Try moving the wheel.
Actual Results:  
In (3) everything works. In (2) scrolling doesn't work.

Expected Results:  
Vertical scrolling should work everywhere, as it does in Konqueror and Opera. The page does not contain frames or iframes or plugins.

Same behavior has been reported for Ubuntu 7.04: 
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty)
(Reporter)

Updated

11 years ago
Version: unspecified → 2.0 Branch
(Reporter)

Comment 1

11 years ago
Same behavior has been reported for Windows platform.
OS: Linux → All
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a5pre) Gecko/20070527 Minefield/3.0a5pre

I see the problem indeed in the version that you're using, but not on trunk so this is fixed.
You can try it out: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.