[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#20871: scroll wheel binding IFRAME?
From:       Tobias Anton <TA () ESC-Electronics ! de>
Date:       2001-03-01 13:06:19
[Download RAW message or body]

On Thursday 01 March 2001 03:23, Peter Silva wrote:
> Tobias Anton wrote:
> > On Saturday 24 February 2001 19:14, peter@basquette.homeip.net wrote:
> >> Package: konqueror
> >> Version: KDE 2.1.0 Beta 2
> >> Severity: wishlist
> >> Installed from:    Mandrake RPMs
> >> Compiler:          Not Specified
> >> OS:                Linux
> >> OS/Compiler notes: fully patched Mdk 7.2
> >>
> >> When there is an IFRAME in a page, and
> >> the mouse is over it, if one uses a mouse
> >> wheel to scroll, the first movement of
> >> the wheel selects the IFRAME, and the
> >> later events are given to the IFRAME, rather
> >> than enclosing page.
> >>
> >> so, scrolling with the arrow keys works, but when the mouse happens to
> >> be over a b anner ad,  mouse wheel scrolling
> >> scrolls the ad, instead of the page.
> >
> > I'd call this a feature: although IFRAMEs are often used for banner ads,
> > you can put complete scrollable pages into the IFRAME.
> > We deliberately have set the focus policy of the IFRAME, exactly of the
> > KHTMLView to WheelFocus, which makes it grab focus when the wheel is
> > turned over it.
>
> Why is the wheel mouse action different from the keyboard binding?
> I would have expected both to scroll the same way, but the mouse
> wheel grabs focus while the keys do not.
The keys do not? Please explain this more detailed - input devices don't grab 
focus, only widgets can.


> > It's a bit hard to decide what to do here - imagine one uses the iframe
> > to display a large page floated in some frame-like decorations. He'd
> > report the bug that IFRAMEs are not scrollable!?
>
> would it be reasonable, in this case, he would click (with a mouse button)
> to get focus, then scroll with the wheel...  (ie.  like "click to focus" wm
> policy.)
You're probably right about this. Unfortunately, QT doesn't work that way: On 
X11, the wheel event is redirected to the widget under the mouse.
This is different for the windows implementation of QT.

Again, this is the only possible solution i see:
> > Maybe we should pop the event to the parent if there's no scrolling
> > possible in the IFRAME?
.. or if it's not focused.

What do you think?

Tobias

[prev in list] [next in list] [prev in thread] [next in thread]