New issue
Advanced search Search tips

Issue 877530 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Aug 29
Cc:
dtapu...@chromium.org
phanindra.mandapaka@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

incognito agent icon covers too much the minimalize button for the detached developer console

Reported by ares...@gmail.com, Aug 24 
Chrome Version       : Version 68.0.3440.84 (Official Build) (64-bit)

What steps will reproduce the problem?
(1) open chrome in incognito mode
(2) open developer console
(3) detach the developer console
(4) hover/click your mouse over differents parts of the "developer console minimize button"

What is the expected result?
mouse hover/click should work on the whole "developer console minimize button".

What happens instead?
only 1/3 of the button is clickable because of the agent incotnito icon covering it [red rectangle means clickable area - see screenshot]

My suggestion:
move agent incognito icon  more to the left and a few pixels to the top

screenshot attached

kind regards, Stefano Kocka
chrome-bug-001.png
2.7 KB View Download

Comment 1 by dtapu...@chromium.org, Aug 24

Labels: Needs-Feedback
What platform is this on?

Comment 2 by ares...@gmail.com, Aug 25 

sorry my bad, Windows 7 x64
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 25

Cc: dtapu...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by susan.boorgula@chromium.org, Aug 26

Labels: Needs-Triage-M68

Comment 5 by phanindra.mandapaka@chromium.org, Aug 29

Cc: phanindra.mandapaka@chromium.org
Labels: Needs-Feedback Triaged-ET
ares308@ Thanks for filling the issue...

Able to reproduce the issue on latest stable 68.0.3440.106 using Windows 7 and not able to reproduce the on latest Beta 69.0.3497.57 and latest chrome 70.0.3535.0 using Windows 7. Attaching screenshot for reference.

@Reporter: Could you please check the issue on chrome beta 69.0.3497.57 its rolling out very soon as stable. Requesting you to please upgrade to latest chrome 69.0.3492.0 . Could you please upgrade to chrome 69.0.3497.57, you can downlad latest chrome builds here:
" https://www.chromium.org/getting-involved/dev-channel ". let us know if issue still persists or not.

Thanks!
877530.beta.PNG
57.1 KB View Download
877530.1.PNG
43.8 KB View Download

Comment 6 by ares...@gmail.com, Aug 29 

Hi, the beta works fine, seems the problem is solved with the next version.(attachment)
thanks for your time and great work on this project.

kind regards, Stefano
capture.png
26.3 KB View Download
Project Member

Comment 7 by sheriffbot@chromium.org, Aug 29

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by dtapu...@chromium.org, Aug 29

Status: Fixed (was: Unconfirmed)
Issue is fixed in M69
►

Sign in to add a comment