Bug 319 - QML WebView buggy with form items, affecting the whole device's usability
: QML WebView buggy with form items, affecting the whole device's usability
Status: RESOLVED FIXED
Product: MeeGo 1.2 Harmattan
Classification: Unclassified
Component: Device
: unspecified
: Normal major with 89 votes (vote)
Assigned To: Ha_Bug
:
Reported: 2011-08-02 13:17 EEST by storsjo
Modified: 2012-02-27 19:46 EET (History)
See Also:
Device name:
Firmware version (*#0000#):

Attachments
A sample application for reproducing the issues (19.40 KB, application/zip)
2011-08-02 13:17 EEST, storsjo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description storsjo 2011-08-02 13:17:37 EEST
Created attachment 29
A sample application for reproducing the issues

The QML WebView has some issues when viewing web pages including forms, mainly
related to the software keyboard.

The main issues are:
- If a software keyboard is opened while on a web page, there's no way of
closing it
- Combo boxes (html <select> elements) don't work if a software keyboard is
present

Steps to reproduce:
0. Build the attached sample application

1. Click the "Open web view" button
2. Click the combo box
3. Notice that the combo box works and that the combo box popup is visible and
the elements are selectable
4. Close the combo box
5. Click the text input field a few times until the software keyboard is opened
6. Notice that the toolbar (including the back button for closing the current
page) is hidden. This isn't an issue in itself.
7. Try to clicking outside of the text input field, trying to close the
software keyboard. Notice that the software keyboard isn't closed.
8. Click the Close html button, which closes the current page via a javascript
callback. Notice that the software keyboard still is open, and no clicks on the
initial page cause it to be closed.
9. Click the "Open web view" button again
10. Try dragging the content of the web view (by pressing the background of the
web page), notice that Flickable reacts properly and scrolls the content
11. Click the combo box
12. Notice that the combo box popup isn't opened
13. Notice that dragging as in step 10 doesn't work any longer.
14. Try to task switch out from the application by swiping - the application is
animated moving out while swiping, but when the swipe has finished, the
application content still is displayed on top, even if some other view of the
phone actually is active (and all presses are sent to that view) . This is a
state where the phone is unusable (for an end user) and needs to be rebooted,
if you can't easily kill the application.

Alternative bug:
1. Kill and restart the application
2. Click the "Open web view" button
3. Click the text input field a few times until the software keyboard is opened
4. Click the combo box
5. Notice that the combo box popup isn't opened
6. Rotate the phone to the other orientation
7. Notice that the content area of the application (except for the software
keyboard) is plain black
Comment 1 storsjo 2011-08-02 14:10:33 EEST
Also, before someone dismisses this as unimportant if it seems complicated to
replicate - it's much easier than that, but the main bug reproduction was a
guided tour around all the bugs I encountered so far. The major bug can be
reproduced directly like this:

1. Start the sample application
2. Click the "Open web view" button
3. Click the text input field a few times until the software keyboard is opened
4. Click the combo box
5. Try to task switch out from the application by swiping - the application is
animated moving out while swiping, but when the swipe has finished, the
application content still is displayed on top, even if some other view of the
phone actually is active (and all presses are sent to that view) . This is a
state where the phone is unusable (for an end user) and needs to be rebooted,
if you can't easily kill the application.
Comment 2 ext-risto.lahti 2011-08-05 07:02:40 EEST
Assigned to internal team. Thank you for your input.
Comment 3 ha_bug 2011-08-05 08:39:52 EEST
(In reply to comment #2)
> Assigned to internal team. Thank you for your input.
Comment 4 storsjo 2011-09-26 16:12:00 EEST
FWIW, the initial report was done with 1.2011.22-6_PR_RM680, this is still
reproducible on 1.2011.34-2_PR_RM680.
Comment 5 storsjo 2011-10-20 16:03:21 EEST
Still reproducible on N950 PR1.1, 2.2011.39-5_PR_RM680.
Comment 6 storsjo 2012-02-27 19:46:12 EET
This seems to be fixed in N9 PR1.2 30.2012.07-1_PR_001.


Nokia Developer aims to help you create apps and publish them so you can connect with users around the world.

?ICP?05048969?  © Copyright Nokia 2011 All rights reserved