New issue
Advanced search Search tips

Issue 692516 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 599362
Owner:
Closed: Feb 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Extentions UI menu missbehaviour

Reported by mynameis...@gmail.com, Feb 15 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Install clear Chrome/Chromium
2. Install any two extentions
3. Hide one of them
4. Go to extentions page
5. Disable the visible one

What is the expected behavior?
Disabled extention is gone and the hidden one is still hidden.

What went wrong?
The hidden extention became visible.

Did this work before? No 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0

 
Components: Platform>Extensions
Labels: -Type-Bug -Pri-2 hasbisect-per-revision M-58 OS-Linux OS-Mac Pri-1 Type-Bug-Regression
Owner: rdevlin....@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows 10, Mac 10.12.2 and Ubuntu 14.04 using chrome reported version #56.0.2924.87 and latest canary #58.0.3013.0.

Bisect Information:
=====================
Good build: 51.0.2667.0  Revision(379160)

Bad Build : 51.0.2668.0  Revision(379426)

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/70810e15c6c90b1e2ff5700d7dc265f6dd276f9b..5d7bad9da15b89c65099a03cdc105cbe906b9b00

From the above change log suspecting below change

Review url: https://codereview.chromium.org/1761913003

rdevlin.cronin@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks...!!

Comment 2 by ajha@chromium.org, Feb 22 2017

Devlin@: Could you please take a look at this.
Mergedinto: 599362
Status: Duplicate (was: Assigned)
This behaviour is very nasty, especially, if a user imports extensions, e.g. via synchronizing with his Google account.
This should be fixed soon, imho!

Sign in to add a comment