3.12 MB, application/x-shockwave-flash
Created attachment 8364174 [details] OSK not sliding into view once the physical keyboard is used If a user uses the physical keyboard while the OSK is visible during a prompt dialog, taping on other prompts will have the input field selected automatically but will not slide in the OSK into view as it did the first time around. To fix this, you can tap on the input field again, the OSK will re-appear and then you can dismiss the prompt dialog by taping either "Cancel" or "OK". The next prompt dialog window will correctly slide in the OSK into view. - Attached a short video, notice that when a new prompt appears, the OSK doesn't slide in automatically as it should. Steps to reproduce the issue: 1) Open Firefox Metro 2) Go to http://dolske.net/mozilla/tests/prompt/sizes.html 3) Select "prompt()" from the list 4) Tap on any prompt (doesn't matter which one is selected as long as it's a prompt) 5) The OSK should appear when the prompt dialog window appears 6) Use the physical keyboard and the OSK should dismiss 7) Once the OSK is dismissed, tap on either "OK" or "Cancel" 8) Tap on another prompt button (you'll notice that the OSK will not slide into view this time around) 9) Tap on the input field and the OSK should slide back into view 10) Dismiss the prompt by taping on either "OK" or "Cancel" 11) Taping on another prompt will now slide in the OSK into view (the original behavior) Current Behavior: Expected Behavior: Found the issue using the following builds: - http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014-01-22-00-40-04-mozilla-aurora/ - http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014-01-22-03-05-21-mozilla-central/
This sounds like a reasonable behavior to me. If the physical keyboard is used we assume you intend to use it and don't need the OSK anymore. The extra input tap on step 9 shows the intent to use the OSK again and form then on. I don't think we need be more aggressive in showing the OSK if a physical keyboard was used.
Expected Windows Behaviour.
After reading through comment #1, I agree with Rodrigo.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.