Bug 33172
Summary: | [Qt] Selection list: Crash observed when onFocus event trigered | ||
---|---|---|---|
Product: | WebKit | Reporter: | Vikram <vikram.malaiya> |
Component: | WebKit Qt | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Critical | CC: | hong.a.zhao |
Priority: | P2 | Keywords: | Qt |
Version: | 528+ (Nightly build) | ||
Hardware: | S60 Hardware | ||
OS: | S60 3rd edition |
Vikram
STEPS TO REPRODUCE:
1. Load link
selection list
http://testsuite.nokia-boston.com/content/esmp_Sec10/selectObject/select_onFocus1.html
http://testsuite.nokia-boston.com/content/esmp_Sec10/selectObject/select_onFocus2.html
2. Verify with page instructions.
ACTUAL RESULTS:
Crash observed when onFocus event triggered
EXPECTED RESULTS:
No crash.
Expected alert(s) appear when element tapped (as instructed on page)
Show ยป STEPS TO REPRODUCE: 1. Load link
selection list http://testsuite.nokia-boston.com/content/esmp_Sec10/selectObject/select_onFocus1.html http://testsuite.nokia-boston.com/content/esmp_Sec10/selectObject/select_onFocus2.html
2. Verify with page instructions. ACTUAL RESULTS: Crash observed when onFocus event triggered EXPECTED RESULTS: No crash. Expected alert(s) appear when element tapped (as instructed on page)
Internally linked to - https://qtrequirements.europe.nokia.com/browse/BR-1067
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Hong Zhao
In the original testcase, when you click on the popup list, the javascript alert box pops up, and when you click on OK button, the focus goes back to the popup list, so that's why you keep on having that alert box as a infinitive loop. It behaves the same in FireFox in Linux. In Windows, The alert box doesn't block in Firefox or IE, that's based on the Windows system, ie. Windows API doesn't sent setfocus event back after close the alert box, while in Linux, it sends setfoucs event from the system. This is not a bug in QTWebKit. The focus should be changed after alert box after the alert box.
Hong Zhao
*** Bug 33175 has been marked as a duplicate of this bug. ***