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

Issue 884880 link

Starred by 1 user
Status: Assigned
Owner:
█ elizabethchiu@chromium.org
Last visit 15 days ago
Cc:
lpalmaro@chromium.org
zalcorn@chromium.org
abodenha@chromium.org
r...@chromium.org
alemate@chromium.org
zork@chromium.org
wzang@chromium.org
jdufault@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression
Team-Accessibility

Blocking:
issue 884886



Sign in to add a comment

Regression: add a new user blocked from advancing on many screens at highest display size

Project Member Reported by leberly@chromium.org, Sep 17 
Chrome 70.0.3538.16 (Official Build) dev (64-bit)
Google_Eve

Steps to reproduce:
# Set the display size resolution to the largest size using either settings while signed in or by using ctrl + shift + plus sign on any screen
# Log out to return to login screen
# Navigate to Add New User
Expected: able to navigate to all screens while in this display size
Actual: most of the screens have the accept or continue buttons behind the blurred out status tray

Screenshots of these screens showing the bug behavior:
wifi connection screen
two step verification
You're signed in!
Once last thing
Play store terms of service - all 3 screens
Google Assistant


Workaround: make the display size smaller but that's not a good option for people who need the larger size


There is a similar bug 882900 - the difference in that case is that the buttons are also off screen or behind the status tray but if you press tab you can bring them into view

Comment 1 by leberly@chromium.org, Sep 17

IMG_20180917_102407578.jpg
164 KB View Download
IMG_20180917_102345206.jpg
315 KB View Download
IMG_20180917_102314657.jpg
468 KB View Download
IMG_20180917_102248741.jpg
284 KB View Download
IMG_20180917_102217513.jpg
223 KB View Download
IMG_20180917_102217513.jpg
223 KB View Download
IMG_20180917_102110802.jpg
140 KB View Download
IMG_20180917_102049440.jpg
224 KB View Download

Comment 2 by leberly@chromium.org, Sep 17

Labels: a11y-q2-18

Comment 3 by leberly@chromium.org, Sep 18 

Last known good build was on beta channel 69.0.3497.95
Change happened with dev channel - currently on 70.0.3538.16

Comment 4 by leberly@chromium.org, Sep 18

Blocking: 884886

Comment 5 by lpalmaro@google.com, Sep 18

Cc: zork@chromium.org
Owner: abodenha@chromium.org
Status: Assigned (was: Untriaged)
@Albert or Zach, could you help to triage this issue please?

Comment 6 by zork@chromium.org, Sep 18

Cc: abodenha@chromium.org
Owner: leberly@chromium.org
leberly@: How did it appear in 69?  Did the status bar change, or did the OOBE screens?  Could you attach a screenshot of it working?

Thanks!

Comment 7 by leberly@chromium.org, Sep 18 

There was a major UI change in M70 and the addition of some screens such as "One last thing". Here are some pictures of the similar UI in M69. 

Also, this happens during the new user Sign In flow which can happen from the login screen.
IMG_20180918_082517353.jpg
192 KB View Download
IMG_20180918_082508444.jpg
276 KB View Download
IMG_20180918_082457723.jpg
368 KB View Download
IMG_20180918_082449109.jpg
254 KB View Download
IMG_20180918_082208573.jpg
432 KB View Download
IMG_20180918_082118720.jpg
150 KB View Download

Comment 8 by leberly@chromium.org, Sep 18

Owner: zork@chromium.org

Comment 9 by r...@chromium.org, Sep 18

Cc: jdufault@chromium.org wzang@chromium.org
Some folks who have worked on the Shelf recently.

Comment 10 by r...@chromium.org, Sep 18

Cc: r...@chromium.org
Owner: jdufault@chromium.org
Jacob, could you help find the correct owner for this?

Comment 11 by jdufault@chromium.org, Sep 18

Owner: alemate@chromium.org

Comment 12 by alemate@chromium.org, Oct 16

Cc: alemate@chromium.org lpalmaro@chromium.org zalcorn@chromium.org
Owner: elizabethchiu@chromium.org
The problem is that WebUI controls get under the shelf.
And depending on the screen, even buttons may be displayed stacked.

I don't have any solution (besides of rethinking the UI part) for this otherwise as to suggest to use keyboard navigation instead.

Assigning to Elizabeth, CC product to decide what to do here.
►

Sign in to add a comment