Closed Bug 273792 Opened 20 years ago Closed 20 years ago

mouse wheel does not control tbody in table with overflow: scroll

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 97283

People

(Reporter: nigel, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041128 Firefox/1.0 (Debian package 1.0-4) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041128 Firefox/1.0 (Debian package 1.0-4) When using a table with a thead, tfoot, and tbody, with the tbody set to a max-height of 29em and overflow:scroll in CSS, when using the mouse wheel in the tbody the tbody will not scroll, nor will the actual page. To draw an analogy, when an iframe is embedded in a page with scrollbars on, if you move the mouse over the iframe and use the mouse wheel, the iframe's content will scroll. In the case of the tbody however, nothing scrolls at all. Reproducible: Always Steps to Reproduce: 1. Visit a page with a table on it, this table needs a tbody with an overflow of scroll (or possibly auto), and a max-height value. The tbody needs to have enough content to make the scrollbars need to be used. 2. Move the mouse over the tbody 3. Try to use the mouse wheel Actual Results: No scrolling occurs, either in the tbody or the browser window. Just as if you're typing in a textarea and try to use the mouse scroll, the window will not move. Expected Results: The tbody should scroll.
Already fixed on the trunk, just too late for 1.0 *** This bug has been marked as a duplicate of 97283 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
(In reply to comment #1) > Already fixed on the trunk, just too late for 1.0 > > *** This bug has been marked as a duplicate of 97283 *** Aah. Searching for "overflow", "mouse", "scroll", "wheel" and the likes never turned anything up... prolly my fault for not understanding fully the god-awful search... Good to know there is a fix in the pipeline though :)
You need to log in before you can comment on or make changes to this bug.