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

Issue 740013 link

Starred by 1 user
Status: WontFix
Owner:
zalcorn@chromium.org
Closed: Jul 2017
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
wuyingbing@chromium.org
█ brajkumar@chromium.org
omrilio@chromium.org
█ blakeo@chromium.org
yhanada@chromium.org
pcovell@chromium.org
█ dvallet@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression


Participants' hotlists:
Fixing-touch


Sign in to add a comment

Regression:In OOBE, On screen keyboard closes abruptly on clicking on spacebar.

Project Member Reported by jbanavatu@chromium.org, Jul 7 2017 
Chrome Version: 61.0.3150.0/9720.0.0 dev channel Kip,Minnie,Daisy
OS: Chrome OS

What steps will reproduce the problem?
(1)Recover build via USB >> Go to Accessibility in OOBE or Uber tray >> Enable On screen keyboard
(2)Now click on space bar in On screen keyboard and Observe.

Expected: In OOBE,Nothing should happen on clicking space bar in On screen keyboard 
Actual: Instead,On screen keyboard closes abruptly .

This is regression issue as same is working fine in 59.0.3071.113/940.67.0
stable channel Kip.

Attaching screen-cast for reference.
Actual.mp4
7.4 MB View Download
Expected.mp4
7.4 MB View Download

Comment 1 by tbuck...@chromium.org, Jul 7 2017

Owner: omrilio@chromium.org
Status: Assigned (was: Untriaged)
@omrilio what do you think? I'm not sure the keyboard should stay active when something like a toggle is focused -- if you're going to be interacting with controls on the screen, you shouldn't need the virtual keyboard to do it (though maybe there's some a11y case I'm not thinking of?).

Comment 2 by oka@chromium.org, Jul 9 2017 

Isn't it the same behavior as when the space key in physical keyboard is pressed instead of a11y keyboard?

Comment 3 by omrilio@chromium.org, Jul 26 2017

Owner: zalcorn@chromium.org

Comment 4 by oka@chromium.org, Jul 26 2017

Cc: wuyingbing@chromium.org
Status: WontFix (was: Assigned)
I think it's WAI. a11y keyboard should have the same behavior as the physical keyboard.

Comment 5 by omrilio@chromium.org, Jul 26 2017 

I am in favor of allowing the user to open the a11y keyboard if they really want to. Note that this is a user action, so absolutely agree that this is WAI.
►

Sign in to add a comment