Bug 40363

Summary: [Qt] Keyboard input issues in plugins (flash) on Maemo5
Product: WebKit Reporter: Dominik Holland <dominik.holland>
Component: WebKit QtAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: benjamin, dave, diegohcg, girish
Priority: P3 Keywords: Qt, QtTriaged
Version: 528+ (Nightly build)   
Hardware: Other   
OS: Other   
URL: http://bugreports.qt.nokia.com/browse/QTBUG-11270

Dominik Holland
Reported 2010-06-09 07:33:01 PDT
ENVIRONMENT: Maemo5 PR1.2 (strictly, PR1.1.1 OR the libqt4-maemo5-* does NOT exhibit this issue) QWebView* qwv = new QWebView(); qwv->connect(qwv, SIGNAL(destroyed()), qApp, SLOT(quit())); qwv->settings()->setAttribute(QWebSettings::PluginsEnabled, true); qwv->load(QUrl("http://www.bubblebox.com/swf6/1380/learn-to-fly.swf")); qwv->showFullScreen(); qwv->show(); qApp->exec(); wait for flash content to load, poke around and then at some point (where the plugin expects keyboard input) press a hardware keyboard button. EXPECTED OUTCOME: Have the button (un)press event be propagated and processed by the flash app (on libqt4-maemo5 this worked) ACTUAL OUTCOME: The flash plugin freezes. REPRODUCIBILITY: always, flashlauncher. Occasionally, a "HIM: x11FilterEvent( _HILDON_IM_COM / ) was not handled" message appears on the console. FlashLauncher from extras-devel exibits this problem well (flashlauncher-experimental which links to libqt4-maemo5 also shows how it used to work). You can also use http://www.bubblebox.com/swf6/1269/shopping-cart-hero.swf as test URL Using the maemo-browser the flashplugin works like expected
Attachments
Diego Gonzalez
Comment 1 2010-07-21 07:04:56 PDT
I can reproduce the same problem
David O'Reilly
Comment 2 2010-09-08 00:42:37 PDT
I can reproduce this problem
Benjamin Poulain
Comment 3 2011-02-23 04:05:01 PST
After discussing with the team, closing as wontfix (unless Girish really want to fix that).
Girish Ramakrishnan
Comment 4 2011-02-24 02:41:03 PST
Not me :) But if anyone wants to fix, I can help them out.
Note You need to log in before you can comment on or make changes to this bug.