Bug 2471 - Selecting all text in an input field causes the virtual keyboard to disappear
: Selecting all text in an input field causes the virtual keyboard to disappear
Status: CLOSED DUPLICATE of bug 2396
Product: Browser
User interface
: 4.0
: All Linux
: Low normal (vote)
: ---
Assigned To: unassigned
: browser-bugs
: http://google.com/
:
:
:
  Show dependency tree
 
Reported: 2007-12-04 00:54 UTC by Michael Wiktowy
Modified: 2007-12-04 23:28 UTC (History)
0 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Michael Wiktowy (reporter) 2007-12-04 00:54:41 UTC
STEPS TO REPRODUCE THE PROBLEM:
Enter a search term in Google. Select it (in order to correct it, replace it,
delete it, etc.) by dragging with the stylus from the end of the entry to the
left of the beginning of the text entry field.
EXPECTED OUTCOME:
The text should be selected and the keyboard should be visible in order to make
changes.

ACTUAL OUTCOME:
The text is selected but keyboard does not appear unless the users tap into the
field again and consequently deselect the selected text. 

REPRODUCIBILITY:
Always.

OTHER COMMENTS:
The problem does depend on dragging just beyond the left border of the input
field. If the user is very careful, they can highlight the entire field without
having the VKB disappearing but it requires quite a bit of manual dexterity.
Presumably the VKB disappearing is intentional since you don't want it around
when you select parts of webpages that have no data entry capability.
Unfortunately, it has an annoying consequence when part of that selected area
is an input field.
Comment 1 timeless 2007-12-04 09:01:53 UTC
fairly good bug report, thanks,

but please search before filing, i'd hope you'd have found the report we have
for this.

*** This bug has been marked as a duplicate of bug 2396 ***
Comment 2 Jake Kunnari 2007-12-04 13:44:32 UTC
Closing DUPLICATE bug reports.
Comment 3 Michael Wiktowy (reporter) 2007-12-04 23:28:07 UTC
Thanks for finding the main bug for this. I did in fact search for this problem
before submitting a bug but "mouseup" and "textarea" were not at the top of my
mind as jargon keywords to try. Next time I will try an advanced search to
search the comment fields also (since I didn't realize that the simple search
didn't do so) as there were some keywords there that would have matched my
jargon of choice.