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

Issue 721345 link

Starred by 3 users
Status: Archived
Owner: ----
Closed: Aug 21
Cc:
█ hdodda@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

The active tab is difficult to discern in Incognito mode

Reported by peters...@gmail.com, May 11 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.96 Safari/537.36

Steps to reproduce the problem:
1. Switch to Incognito mode
2. Bring up two tabs

What is the expected behavior?
It should be easy to know which is the active tab.

What went wrong?
In non-Incognito mode, the lighter tab is the active one. In Incognito mode, the lighter tab is the inactive one. This inconsistency leads me to close the wrong tab out of habit, when I've finished reading a page. This is especially annoying because in Incognito mode you cannot "Reopen Closed Tab".

Did this work before? N/A 

Chrome version: 58.0.3029.96  Channel: n/a
OS Version: 10.0
Flash Version: 

A possible solution might be to draw a black edge around the tab and the top of the screen to make the selected tab clearer. (And, ideally, do the same in the non-Incognito mode, for consistency). In Incognito mode, the tab edge is currently a lighter gray than the tab itself, which just makes the edge look fuzzy.

Comment 1 by ranjitkan@chromium.org, May 12 2017

Labels: Needs-Triage-M58

Comment 2 by hdodda@chromium.org, May 12 2017

Cc: hdodda@chromium.org
Labels: -Type-Bug -Pri-2 -Needs-Triage-M58 hasbisect-per-revision M-60 Pri-1 Type-Bug-Regression
Status: Untriaged (was: Unconfirmed)
Tested the issue on windows 10 & 7 using latest chrome stable M58 #58.0.3029.110  and canary M60 #60.0.3097.0 and issue is reproduced.

Issue is regression issue broken in M53 and is seen only in windows :

Using the per-revision bisect providing the bisect results,
Good build:53.0.2748.0(Revision:395748).
Bad build:53.0.2750.0 (Revision:396337).

You are probably looking for a change made after 396300 (known good), but no later than 396306 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspectas some perf builds might get missing due to failure.

 https://chromium.googlesource.com/chromium/src/+log/e623eb7cd1fc6d7cef93a133c4742c42da96b76c..7b8323249aac91b1c7e51d880584fd102934cb7e

Unable to find the suspect from the above CL , could someone please help us in assigning it to the concern owner.

Thanks!

Comment 3 by robliao@chromium.org, Aug 21

Status: Archived (was: Untriaged)
Archiving old bugs that haven't been actively assigned in over a year.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
►

Sign in to add a comment