New issue
Advanced search Search tips

Issue 873427 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Wrong Keyboard Appears If Switching From Tel Type Keyboard

Reported by gpul...@gmail.com, Aug 11

Issue description

Steps to reproduce the problem:
1. Launch Attached Test Page On An Android Phone
2. Tap The Top Entry Box To Bring Up A Phone-Style Keypad
3. Tap the Bottom Entry Box And The Keypad The Launches is in the symbol state and NOT the alphabet state.  Had you started with the bottom keypad it would have brought up the correct keyboard.

What is the expected behavior?
Tapping the bottom input box should always bring up the alphabet keypad and should be consistent.

What went wrong?
The keypad that comes up depends on whether you have just launched a telephone type keypad.  It should be independent.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 68.0.3440.91  Channel: n/a
OS Version: 8.0.0
Flash Version: 

I'm guessing this is a common issue when someone has a phone and password entry on a page.  They probably ignore the bug and just make the user hit the ABC button to find the letters.
 
test.html
111 bytes View Download
Labels: Needs-triage-Mobile
Labels: -Hotlist-Interop
Cc: jbanavatu@chromium.org chelamcherla@chromium.org
Components: UI>Input>Text
Labels: Needs-Feedback Triaged-Mobile
Tested the issue on Nexus 6p OS 8.0 using chrome #68.0.3440.91 and unable to reproduce this issue. 

Steps:
1. Launch chrome >> Open test html file
2. tap on first input box(here phone style keypad is seen)
3. tap on second input box and observed alphabet keypad

Attaching screen-cast for reference.

@Reporter: Could you please upgrade chrome to latest stable 69.0.3497.100 and check? Also please confirm device details your seeing this issue.

Thanks!
20180925_165816.mp4
2.2 MB View Download
Status: WontFix (was: Unconfirmed)
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.

Thanks!

Sign in to add a comment