CLOSED INVALID 15094
[S60] OfferKeyEventL on Browser Control causes KERN-EXEC 3
https://bugs.webkit.org/show_bug.cgi?id=15094
Summary [S60] OfferKeyEventL on Browser Control causes KERN-EXEC 3
Misha
Reported 2007-08-27 13:06:53 PDT
iBrCtlInterface->OfferKeyEventL( aKeyEvent, aType ); with parameters aType EEventKeyUp and aKeyEvent.iScanCode 167 (EStdKeyDevice3) and keyEvent.iCode = EKeyDevice3 causes KERN-EXEC 3. Steps to reproduce: 1. Start BrCtl. 2. A Flash file is playing within a XHTML page. 4. Press the CENTER key to give the Flash object focus. 5. Observe that if you use the Up and Down arrow keys the Flash object is not scrolling within the XHTML page. Conclusion: The Flash object has focus. 6. Press the application key to return to the shell. 7. Hold the application key to list the running applications and select BrCtl using the CENTER key. Actual outcome BrCtl has closed. Expected outcome BrCtl is still in the list of running applications.
Attachments
Patch file for PluginWin.cpp (1.46 KB, patch)
2007-08-27 13:10 PDT, Misha
Sachin.Padma: review-
Patch (45.65 KB, patch)
2007-09-04 09:05 PDT, Misha
Sachin.Padma: review+
Misha
Comment 1 2007-08-27 13:10:15 PDT
Created attachment 16136 [details] Patch file for PluginWin.cpp If BrCtl is created without cursor capability WebKitCursor is NULL. The fix includes NULL check for WebKitCursor in PluginWin.
Sachin Padma
Comment 2 2007-08-31 11:31:43 PDT
Comment on attachment 16136 [details] Patch file for PluginWin.cpp This should be modified so that in Tab navigation mode we do not notify plugins of the position and activated and deactivated cases.
Misha
Comment 3 2007-09-04 09:05:08 PDT
Sachin Padma
Comment 4 2007-09-06 06:59:18 PDT
Comment on attachment 16196 [details] Patch r=me
Bradley Morrison
Comment 5 2008-04-09 11:31:55 PDT
Bulk update of s60 bugs - tagging and closing.
Bradley Morrison
Comment 6 2008-04-09 11:39:37 PDT
Bulk closing of all s60 platform bugs. Sorry for the noise!
Joel Parks
Comment 7 2011-03-21 11:53:37 PDT
re-purposing InTSW keyword for use by QtWebkit team
Note You need to log in before you can comment on or make changes to this bug.