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

Issue 845874 link

Starred by 4 users
Status: WontFix
Owner:
zalcorn@chromium.org
Closed: Jul 10
Cc:
ajha@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
Team-Accessibility



Sign in to add a comment

Regression: On screen keyboard overlapping on Ubertray when in floating mode

Project Member Reported by kebalaji@chromium.org, May 23 2018 
Chrome Version: 68.0.3437.0/10705.0.0 dev-channel Daisy,Candy and Reks
OS: Chrome OS

What steps will reproduce the problem?
(1)Recover build>. Enable On screen keyboard, change it from docking mode to floating mode and observe

Expected: Ubertray is not seen when On screen keyboard is in floating mode
Actual: Chopped ubertray is seen and when clicked on that Ubertray menu is seen behind the keyboard

This is a Regression issue as same is working fine in 67.0.3369.0/10490.0.0 dev

@blakeo: Please confirm the issue
Actual_vk.mp4
3.0 MB View Download
Expected_VK.mp4
2.6 MB View Download

Comment 1 by blakeo@chromium.org, May 28 2018

Owner: omrilio@chromium.org
I'm not a PM but I'm inclined to say this is WAI. The padding itself wasn't a regression and was added for aesthetic purposes. Since the tray is still mostly covered by the keyboard, visibility of the ubertray while the floating keyboard is in the default location doesn't seem like it should be considered a primary user workflow. That said, I'm happy to remove the margin if need be.

+Omri: WDYT?

Comment 2 by omrilio@chromium.org, Jun 1 2018

Owner: zalcorn@chromium.org
To zach since this is on OOBE, decide on expected behavior and we can adjust.

Comment 3 by zalcorn@chromium.org, Jun 1 2018 

Omri, what's the expected behavior for floating keyboard + ubertray in-session? We should match that in OOBE.

Comment 4 by zalcorn@chromium.org, Jul 10

Status: WontFix (was: Assigned)
Looks like it behaves the same in-session so I'm okay with having that consistent in OOBE. I'm going to close as WontFix.
►

Sign in to add a comment