Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 7 submissions in the queue.

Google Removes Plugin Controls From Chrome

posted by cmn32480 on Tuesday January 31 2017, @02:31PM   Printer-friendly
from the next-they-will-kill-kenny dept.

MrPlow writes:

Submitted via IRC for TheMightyBuzzard

Google made a change in Chrome 57 that removes options from the browser to manage plugins such as Google Widevine, Adobe Flash, or the Chrome PDF Viewer.

If you load chrome://plugins in Chrome 56 or earlier, a list of installed plugins is displayed to you. The list includes information about each plugin, including a name and description, location on the local system, version, and options to disable it or set it to "always run".

You can use it to disable plugins that you don't require. While you can do the same for some plugins, Flash and PDF Viewer, using Chrome's Settings, the same is not possible for the DRM plugin Widevine, and any other plugin Google may add to Chrome in the future.

Starting with Chrome 57, that option is no longer available. This means essentially that Chrome users won't be able to disable -- some -- plugins anymore, or even list the plugins that are installed in the web browser.

Please note that this affects Google Chrome and Chromium.

Source: http://www.ghacks.net/2017/01/29/google-removes-plugin-controls-from-chrome/

Original Submission

 
This discussion has been archived. No new comments can be posted.
Google Removes Plugin Controls From Chrome | Log In/Create an Account | Top | 78 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 1) by charon on Tuesday January 31 2017, @07:25PM

    by charon (5660) on Tuesday January 31 2017, @07:25PM (#461382) Journal
    I had a similar problem with PaleMoon. My bank's website would not recognize it as a compatible browser for a long time. A recent update (27 something) fixed that and now it's my primary browser.

  • (Score: 0) by Anonymous Coward on Wednesday February 01 2017, @05:21AM

    by Anonymous Coward on Wednesday February 01 2017, @05:21AM (#461560)

    My bank's website would not recognize it as a compatible browser

    Crazy question: You did try a User Agent Switcher to spoof the site and tell it you were using something on their brain-dead list. Right?
    ...and proper sniffing[1] only looks for the rendering engine--not the browser name.

    [1] Browser sniffing is mostly unnecessary.
    If a site is built to be standards-compliant, any standards-compliant browser will work on it.
    Setting up their landing page so that you can't get through it with a non-standards-compliant browser should do the trick without stupid shit like browser sniffing.
    (I'm flashing back to Acid2 & Acid3 here.)

    Does your bank's front page even pass the validator? [w3.org]

    -- OriginalOwner_ [soylentnews.org]

    • (Score: 1) by charon on Wednesday February 01 2017, @09:43AM

      by charon (5660) on Wednesday February 01 2017, @09:43AM (#461601) Journal

      Yes and it still didn't work. There was something lacking in the browser until somehow it was there in an update I had skipped. And it's not that it was a huge amount missing, the only thing it balked at doing was some crazy javascript thing for transferring money between accounts. Displayed everything just fine.

      It seems to validate except for a couple missing alt text on img errors.