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

Issue 608284 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 603010
Owner:
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Chrome developer console - dark theme - scroll bar arrows not visible

Reported by gerald.l...@gmail.com, May 2 2016

Issue description

Chrome Version       : 49.0.2623.112
OS Version: 6.3
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5: N/A
  Firefox 4.x: N/A
     IE 7/8/9: N/A

What steps will reproduce the problem?
0. Using Windows 8
1. In Chrome Browser, hit F12 key to open console
2. Hit F1 key to open the Settings area
3. Under the Appearance section, select the Dark theme
4. Click the "x" in the upper right-hand-corner to close the Settings window
2. Hit CTRL+O to open a file
3. No scroll bar arrows are visible anywhere in the console

What is the expected result?
==> User should be able to see up/down/left/right arrows at the ends of the console scroll bars

What happens instead of that?
==> Can't see up/down/left/right arrows.

Please provide any additional information below. Attach a screenshot if
possible.
==> Most likely can't see down arrows because arrows are dark colored on a dark background (see attached image).

UserAgentString: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36

 
chrome-console-dark-theme-down-arrows-not-visible.jpg
60.6 KB View Download
Cc: ashej...@chromium.org
Components: Platform>DevTools UI>Browser>Themes
Labels: -Pri-3 M-52 OS-All Pri-2
Status: Untriaged (was: Unconfirmed)
The above issue is reproducible on All-OS (Windows (10 & 7), Mac 10.11.4 & Ubuntu 14.04) with chrome versions : 50.0.2661.94(Stable), 51.0.2704.22(Beta) & 52.0.2722.0(Canary). When hit 'Ctrl+O' scroll bar not visible.

This is a non regression issue as can be seen from M49 build from where it this was introduced. Hence marking the same as Untriaged.

Thank you!

Comment 2 by alph@chromium.org, May 6 2016

Owner: pfeldman@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Mergedinto: 603010
Status: Duplicate (was: Assigned)

Sign in to add a comment