Summary: | [Qt] Infinite loop (leading to crash) when setting cursor in QGraphicsWebView | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Antonio Gomes <tonikitoo> | ||||
Component: | WebKit Qt | Assignee: | Antonio Gomes <tonikitoo> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Critical | CC: | ariya.hidayat, hausmann, kenneth, vestbo | ||||
Priority: | P1 | Keywords: | Qt | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | All | ||||||
Bug Depends on: | |||||||
Bug Blocks: | 29799, 30557, 30558 | ||||||
Attachments: |
|
Description
Antonio Gomes
2009-10-19 19:26:10 PDT
Created attachment 41470 [details] (commit in r49846) patch 0.1 - late emission of CursorChange event. QWebView works because QWidget emits the CursorChange event just like the proposed patch does (at the end of the setCursor method): void QWidget::setCursor(const QCursor &cursor) { Q_D(QWidget); (...) setAttribute(Qt::WA_SetCursor); d->setCursor_sys(cursor); QEvent event(QEvent::CursorChange); QApplication::sendEvent(this, &event); } Seems like a workaround. Shouldn't this be fixed in Qt instead? Right now it seems that with QWidgets, the event is being called after the cursor has been set, and that that is not the case with QGraphicsWidgets. That is different behaviour and if that is not intentional (which I guess not), it can be considered a bug. Comment on attachment 41470 [details] (commit in r49846) patch 0.1 - late emission of CursorChange event. clearing r+ flag since patch has landed. as i talked to ariya on irc and pointed out in bug description and comment #2, i agree w/ kenneth that it has to be investigated in qt side about why such behaviour, however i do not need we have to be crashy until then. So i am landing the fix/workaround and filing to followup bugs: 1) one for auto test this 2) for investigating the real reason on why qt differ from qwidget to qgraphicsitem here. (In reply to comment #5) > as i talked to ariya on irc and pointed out in bug description and comment #2, > i agree w/ kenneth that it has to be investigated in qt side about why such > behaviour, however i do not need we have to be crashy until then. So i am > landing the fix/workaround and filing to followup bugs: > > 1) one for auto test this > 2) for investigating the real reason on why qt differ from qwidget to > qgraphicsitem here. 1) 30557 2) 30558 |