New issue
Advanced search Search tips

Issue 710733 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Explain what happened to chrome://plugins

Reported by term...@gmail.com, Apr 12 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Firefox/52.0

Steps to reproduce the problem:
1. Go to chrome://plugins, it no longer exists
2. In 57.0.2987.133 it says "This site can’t be reached"

What is the expected behavior?
Basically I expected to be able to disable plugins using chrome://plugins as I have before. Judging by a quick google search there are a number of reports of this. I think you should at least change that page to explain to the user why it no longer exists.

Or you could always bring it back :) I found the "disable" for flash but apparently it's not really the same. Why can't I disable DRM plugins entirely to stop them from loading?

Refer to #615738 and #688747.

What went wrong?
This site can’t be reached

The webpage at chrome://plugins/ might be temporarily down or it may have moved permanently to a new web address.
ERR_INVALID_URL

Did this work before? Yes 

Chrome version: <Copy from: 'about:version'>  Channel: stable
OS Version: 6.0 (Windows Vista, Windows Server 2008)
Flash Version: Shockwave Flash 25.0 r0
 
Status: WontFix (was: Unconfirmed)
Chrome://plugins page is deprecated completely, please check  issue 615738  for more info.

Thanks!

Comment 2 by term...@gmail.com, Apr 12 2017

Right, I'm aware of that. My suggestion is you change that page to say why you deprecated it and then tell users what to do. The reason I suggest that is because people depend on it and you've gotten rid of it. There should be some transition.

Sign in to add a comment