Bug 136890 - Iframe contents cannot be scrolled using a mouse if display = 'none' has been applied
Summary: Iframe contents cannot be scrolled using a mouse if display = 'none' has been...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Macintosh Intel OS X 10.9
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-17 08:56 PDT by Aaron Quamme
Modified: 2016-09-26 09:28 PDT (History)
4 users (show)

See Also:


Attachments
Test case for the iframe scrolling bug (1.16 KB, application/zip)
2014-09-20 16:15 PDT, Aaron Quamme
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Quamme 2014-09-17 08:56:01 PDT
After applying then removing the display value of 'none' to an iframe, mouse scrolling doesn't work. Once focus is given to the iframe the frame can be navigated with keyboard controls, but mouse scrolling remains nonfunctional. 

Workaround : changing the size of the frame restores correct behavior.

A test case has been provided in the attached file.
Comment 1 Brent Fulgham 2014-09-19 17:03:36 PDT
(In reply to comment #0)
> After applying then removing the display value of 'none' to an iframe, mouse scrolling doesn't work. Once focus is given to the iframe the frame can be navigated with keyboard controls, but mouse scrolling remains nonfunctional. 
> 
> Workaround : changing the size of the frame restores correct behavior.
> 
> A test case has been provided in the attached file.

No test case attached!
Comment 2 Aaron Quamme 2014-09-20 16:15:32 PDT
Created attachment 238418 [details]
Test case for the iframe scrolling bug
Comment 3 Aaron Quamme 2014-09-20 16:16:36 PDT
(In reply to comment #1)
> (In reply to comment #0)
> > After applying then removing the display value of 'none' to an iframe, mouse scrolling doesn't work. Once focus is given to the iframe the frame can be navigated with keyboard controls, but mouse scrolling remains nonfunctional. 
> > 
> > Workaround : changing the size of the frame restores correct behavior.
> > 
> > A test case has been provided in the attached file.
> 
> No test case attached!

My apologies. I've attached it.
Comment 4 Aaron Quamme 2014-10-22 14:25:41 PDT
This is still reproducible in Webkit r174761.