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

Issue 696963 link

Starred by 0 users
Status: Archived
Owner: ----
Closed: Aug 21
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Non-regression:Unable to perform any action in 3 dot menu of tabs from other device section.

Project Member Reported by sahitya....@techmahindra.com, Feb 28 2017 
Chrome Version: 58.0.3026.0
OS: Ubuntu 14.04,Windows

What steps will reproduce the problem?
(1)launch chrome and login with valid credentials and navigate to the history page and then logout.
(2)login with another credentials in the same person and then navigate to the history page-->>tabs from other devices section.
(3)click on the 3 dot menu and click on hide for now and observe

Expected result:should be able to hide after clicking on hide for now in 3 dot menu. 
Actual result:Instead not bale to hide after clicking on the 3 dot menu.

Note:This is non regression issue seen from M-54
Actual tabs from other devices.ogv
5.8 MB View Download

Comment 1 by brajkumar@chromium.org, Feb 28 2017

Labels: OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on Mac OS 10.12 using chrome latest Dev #58.0.3026.0.

Comment 2 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!

Comment 3 by robliao@chromium.org, Aug 21 

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!

Comment 4 by robliao@chromium.org, Aug 21 

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