New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 817177 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug
Proj-XR
Proj-XR-VR



Sign in to add a comment

VR: Support keyboard for native ui elements

Project Member Reported by vsupruniuk@google.com, Feb 28 2018

Issue description

Chrome Version: 66.0.3356.0
OS: Android

Reproduction steps:

1. Open chrome://flags and enable required flags:
	#vr-browsing-native-android-ui
	#vr-web-input-editing
   Relaunch Chrome
1. Access https://www.tutorialspoint.com/javascript/javascript_dialog_boxes.htm on the test device
3. Enter Chrome VR
3. Scroll down to find section "Prompt Dialog Box"
4. Click “Click Me” button to open Prompt dialog box


What is the expected result?
- Prompt Dialog Box appears, text input field is editable using virtual keyboard

What happens instead?
- Virtual keyboard doesn't appear if to focus on text input field

 
Owner: ymalik@chromium.org
Status: Assigned (was: Untriaged)
Yash, this is likely expected behavior at the moment.  If you could mention the future support plan and reset (or clear) the target milestone, that'd be great.
Labels: -Restrict-View-Google
Components: UI>Browser>VR
Cc: asimjour@chromium.org
Labels: -M-66 M-67
Summary: VR: Support keyboard for native ui elements (was: JS prompt dialog doesn't support keyboard input in VR browsing)
Supporting keyboard on native UI (e.g JS prompt, search box on history, bookmarks) is not in scope for M66.


Comment 5 by bshe@chromium.org, Mar 7 2018

On TOT, I found the behavior of input box in JS prompt and search box on history different. Android 2D VK suppress for the JS prompt case but shows up at the search box case. 
Blocking: 808722

Comment 7 by ericde@google.com, Mar 21 2018

Blocking: -808722
Labels: -M-67 M-68 Hotlist-VRB-MVP-Next
per gordonbrander@ and skonig@, this is not part of critical user journey given usage is so low. Moving to MVP-NEXT and removing this as blocking 808722.

Comment 8 by ymalik@chromium.org, Apr 17 2018

Owner: asimjour@chromium.org
Assigning to Amir for now, please re-assign as needed.
Labels: VRB-Next-Triage
Cc: acondor@chromium.org
Owner: ----
Status: Available (was: Assigned)

Comment 11 by samdrazin@chromium.org, Today (17 hours ago)

Labels: -M-68 VR-B-Input

Sign in to add a comment