Pre-installed Extensions that are blacklisted still shows under Chrome://extensions
Reported by
dvaks...@gmail.com,
May 18 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.48 Safari/537.36 Steps to reproduce the problem: 1. Install an extension. 2. Blacklist the extension. 3. Now the extension still appears, but it is disabled. The problem is, the user can still click on the button to enable it (so it appears to be enabled). However, when refreshing the page, it appears disabled again. What is the expected behavior? 1) Users should NOT be able to change the button (for enabled/disabled) at all as that gives a false indication that it can be enabled. What went wrong? Users were able to change the enabled/disabled button to indicate that the extension was enabled. Did this work before? No Chrome version: 67.0.3396.48 Channel: beta OS Version: 10.0 Flash Version:
,
May 21 2018
dvaksvik@ Thanks for the issue. Tested this issue on Windows 10 on the reported version 67.0.3396.48 and the latest Canary 68.0.3436.0 by following the below steps. 1. Launched Chrome and added Google Keep extension. 2. Navigated to chrome://extensions page and can see no option to blacklist the extension. Request you to provide the screen cast of the steps followed to reproduce the issue. Thanks..
,
Jun 4 2018
I have created a video available from this link (https://imfbox.box.com/s/uc9jqbygx1bixea589ojf3kvpx9dkr9b) to show what is confusing.
,
Jun 4 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 8 2018
dvaksvik@ Thanks for the update. Tested this issue on Windows 10 and Mac OS 10.13.3 on the latest Beta 68.0.3440.17 and Canary 69.0.3452.0 and unable to reproduce the issue. 1. Launched Chrome and added 'Dashlane - Password Manager' extension. 2. Navigated to chrome://extensions and Enabled the extension. 3. When refreshing the page, cannot see the extension being disabled. Attached is the screen cast for reference. Request you to retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations. Thanks..
,
Nov 22
**UI mass Triage** We were unable to reproduce this bug on windows using latest canary-72.0.3617.0 . If this bug still reproduces for you, please reopen or file a new issue. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, May 20 2018