Bug 29388 – [Qt] QtWebKit interprets Qt::XButton1 and 2 as clicks

• Status: RESOLVED
• Resolution: WORKSFORME
• Component: Platform

[Tor Arne Vestbø]

This bug report originated from issue QTBUG-2926
<http://bugreports.qt.nokia.com/browse/QTBUG-2926>

--- Description ---

The demo browser is enough to reproduce this issue. Clicking with an XButton on a link will actually follow that link. History navigation never works.

[Robert Hogan]

Um, what is an X-Button?

Google tells me that 'xbutton qt' is the close button on a window, but that can't be right!

[Kent Hansen]

(In reply to comment #1)
> Um, what is an X-Button?
> 
> Google tells me that 'xbutton qt' is the close button on a window, but that
> can't be right!

From looking at the Qt code, it appears to be the 4th and 5th mouse button on mice that have such.
For example, http://www.microsoft.com/whdc/archive/5b_wheel.mspx

[Robert Hogan]

(In reply to comment #2)
> (In reply to comment #1)
> > Um, what is an X-Button?
> > 
> > Google tells me that 'xbutton qt' is the close button on a window, but that
> > can't be right!
> 
> From looking at the Qt code, it appears to be the 4th and 5th mouse button on
> mice that have such.
> For example, http://www.microsoft.com/whdc/archive/5b_wheel.mspx

I have two extra buttons on the side of my mouse - clicking them follows links in Konqueror but not in QtLauncher. The buttons are completely unresponsive in QtLauncher (Linux). So is this bug valid?

[Kent Hansen]

(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > Um, what is an X-Button?
> > > 
> > > Google tells me that 'xbutton qt' is the close button on a window, but that
> > > can't be right!
> > 
> > From looking at the Qt code, it appears to be the 4th and 5th mouse button on
> > mice that have such.
> > For example, http://www.microsoft.com/whdc/archive/5b_wheel.mspx
> 
> I have two extra buttons on the side of my mouse - clicking them follows links
> in Konqueror but not in QtLauncher. The buttons are completely unresponsive in
> QtLauncher (Linux). So is this bug valid?

It looks like the reporter is expecting the same behavior as in FireFox (http://forums.mozillazine.org/viewtopic.php?f=38&t=358992&start=0).
I don't know what the behavior is in other browsers. Having the same behavior as Safari would make sense.

[Tor Arne Vestbø]

In QWebPage we ignore clicks from buttons unknown to WebCore (anything other than left, middle, right), so if a x-button actually transfers to a normal left button click this test in PlatformMouseEventQt is failing:

    if (event->button() == Qt::LeftButton || (event->buttons() & Qt::LeftButton))
        m_button = LeftButton;
    else if (event->button() == Qt::RightButton || (event->buttons() & Qt::RightButton))
        m_button = RightButton;
    else if (event->button() == Qt::MidButton || (event->buttons() & Qt::MidButton))
        m_button = MiddleButton;
    else
        m_button = NoButton;

Regarding the behavior of navigating the history with xbutton, I would say this is a browser feature.

[Tor Arne Vestbø]

Tried this with a fancy-mouse on mac and we receive the buttons as Xbutton1 and 2, and they are not propagated.