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

Issue 790880 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
█ krajshree@chromium.org
bsep@chromium.org
pkasting@chromium.org
█ brettw@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

No focused tab after ctrl-W

Project Member Reported by rpop@chromium.org, Dec 1 2017 
Chrome Version: 64.0.3281.1 (Official Build) canary SyzyASan (32-bit) (cohort: ASAN)
OS: Win10

What steps will reproduce the problem?
(1) open some tabs
(2) close the focused one with ctrl-W

What is the expected result?
Tab closes, next tab is given "active" UI state in tabstrip

What happens instead?
All tabs are in inactive state (see attachment)

Please use labels and text to provide additional information.
--site-per-process is on, but I haven't flipped any other flags.
no_active_tabs.PNG
15.4 KB View Download

Comment 1 by bsep@chromium.org, Dec 1 2017 

Doesn't reproduce for me, even with site-per-process on. Does it have something to do with the websites you have open?

I tested with 64.0.3281.0 (Official Build) canary (64-bit) (cohort: Clang-64), so I guess it could be related to ASAN too?

Comment 2 by rpop@chromium.org, Dec 1 2017 

I have 100% repro on canary across two different profiles, with lots of different open sites. Attaching my variations hashes.
variations.txt
1.5 KB View Download

Comment 3 by krajshree@chromium.org, Dec 1 2017

Cc: krajshree@chromium.org
Labels: Triaged-ET Needs-Feedback Needs-Triage-M64
Unable to reproduce the issue on Win-10 using chrome reported version #64.0.3281.1 (Official Build) canary SyzyASan and latest canary #64.0.3281.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Launched chrome browser.
2. Opened few tabs.
3. Closed the focused one with ctrl-W
4. Observed that the tab closed and next tab was given "active" UI state in tabstrip as expected.

Note: Even launching chrome using --site-per-process flag did not reproduce the issue.

rpop@ - Could you please check the screen cast and please let us know if anything missed from our side.

Thanks...!!

Comment 4 by rpop@chromium.org, Dec 1 2017

Cc: brettw@chromium.org
Status: WontFix (was: Unconfirmed)
This happened because I had brettw's experimental tab mode turned on and forgot about it.
►

Sign in to add a comment