Issue metadata
Sign in to add a comment
|
A11y: Chrome profile dialog too large for magnified screen |
||||||||||||||||||||||
Issue descriptionGoogle Chrome 63.0.3236.0 (Official Build) canary (64-bit) (cohort: 64-Bit) Windows 10 Enterprise Version 10.0.14393 Build 14393.1715 Monitor set in Windows settings to be 200% magnified (no software magnifiers nor screen readers used) What steps will reproduce the problem? (1) Magnify monitor to 200% (see above note - only in Windows settings) (2) Click on name to sign into Chrome (3) Note that Browse as Guest and Add person buttons are off the screen and note that there is no way to scroll down or resize (4) Set monitor magnification back to 100%, dialog easily fits screen
,
Oct 10 2017
Thanks leberly@ for reporting! - could also attach a screenshot of Step(3)? - could you try to find and add a UI>[component] under "Components" field to help triage?
,
Oct 10 2017
Hi Hwi, I added the UI>Browser>Profiles component. Attached is a screenshot that shows the problem clearly. In this example, I use multiple monitors: one large monitor and one laptop monitor. In the Windows settings, the large monitor is on top of the laptop monitor. You'll see in the screenshot that the dialog actually spills over from the top monitor onto the laptop monitor below. If I just use the laptop with no external monitor, the bottom of the dialog is completely off the screen since there are no other monitors for it to overflow on to. Thanks, Laura
,
Oct 11 2017
Thanks for c#3, Laura. A recommended behavior is to resize the window height to fit within the viewport height.
,
Oct 11 2017
Thanks, Hwi. This bug now belongs to the UI>Browser>Profiles group. I am moving to Untriaged so that they may triage themselves. Please let me know if you have any questions.
,
Oct 13 2017
Mihai, this looks like a Desktop/Web UI issue. Should I reassign it to Scott?
,
Oct 16 2017
,
Nov 3 2017
re: c#4: If by view-port you are referring to the browser view-port, then that would not work if I have a small browser window. Please see screenshot for the scenario I'm describing. We could try to limit the user-manager window's max-width/height to be the monitor's width/height. If we do this, we'll need to keep in mind that sometimes the content will overflow the user-manager window and it'll have to scroll (both horizontally and vertically). Please see second screenshot as reference for this.
,
Nov 3 2017
Thanks a lot for looking into the issue scottchen@! Viewport in c#4 meant the monitor screen viewport (my bad for the unclarity). Your suggestion in c#8, i.e. "limit the user-manager window's max-width/height to be the monitor's width/height", sounds reasonable as long as the scrollbars are shown only for the overflow cases. This approach will allow content and controls to be viewable. Thanks!
,
Dec 4 2017
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 14 2017
,
Dec 15 2017
,
Aug 1
,
Sep 3
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 18
,
Sep 18
,
Sep 18
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by leberly@chromium.org
, Oct 10 2017Labels: -Pri-3 Pri-2