1.8.755.3 forgets plugin disabled state. Can't permanently disable flash anymore!
dieterga last edited by
When I disable a plugin in snapshot 1.8.755.3 on vivaldi://plugins (like flash and widevine), they are again enabled after restarting Vivaldi. This means I can no longer completely disable flash!!
I hope this is a bug in Vivaldi and not related to recent Chrome versions having lost this ability (https://betanews.com/2017/01/30/chrome-57-plugins/)
ElkMonster last edited by
Same on Linux. Unfortunately, this breaks audio playback for me on at least one site that I visit quite frequently (http://www.deutschlandfunk.de). Until one of the last 1.7 snapshots, audio playback on that site would just work if the Flash plugin was disabled (if enabled, attempting to listen to something just does nothing). Now, I need to disable the plugin again every time Vivaldi is restarted.
CantankRus last edited by CantankRus
Although the flash plugin still appears to be enabled you'll find that flash is globally blocked now by looking at the setting
(hit the "content settings button and scroll down to flash)
You can then allow/disallow flash on a per site basis by clicking on the icon in the left side of the address bar.
For a site I visit, I also need to enable the setting "prefer-html-over-flash" in vivaldi://flags to get an alternative non-flash player.
This was unfortunately a change that Google made and that Vivaldi inherited. To give you some background, the Plugins UI was created back in the day when plugins were an essential part of the web experience. However, today, Google Chrome ships with only 3 plugins (Flash, Widevine CDM, and the PDF viewer), and NPAPI (Netscape) plugins are no longer supported. Furthermore, Google now considers Widevine and the PDF viewer to be components of Chrome, not "true" plugins, leaving Flash as the lone external non-Google component. As a result, they made the decision to remove chrome://plugins with the intention to control Flash through a dedicated UI.
Here are some of the relevant bugs with more information:
Google initially planned to dump chrome://plugins in one fell swoop. Then they decided to do it in two phases: Midway through the Chrome 56 cycle, in Chrome 56.0.2924.87, Google engineers suddenly (and unexpectedly) removed the user-facing chrome://plugins UI but left the underlying code compiled into the browser. (We should have seen this change go into Vivaldi 1.7 but the intrepid Vivaldi developers tried to undo it; they successfully reverted the UI change but apparently not the code that reactivates deactivated plugins.) I'm pretty sure that in Chrome 57, Google has completely removed chrome://plugins (UI and underlying code) from the codebase.
I have no idea how Vivaldi will deal with the upcoming changes when they integrate Chromium 57 into v1.8. It doesn't make sense to resurrect chrome://plugins in its entirety, especially if Google decides to make even more changes to how plugins work within the browser. (Eventually, Widevine and the PDF viewer won't even be plugins anymore.) Hopefully Google will develop a better way to control Flash in response to all the negative feedback that they've received so far.
ElkMonster last edited by
@CantankRus Wow, thanks a lot,
chrome://flags/#prefer-html-over-flashhelps a lot! I wonder why Flash is preferred over HTML(5) by default. Who'd want that nowadays? ;)
@xyzzy Thanks for the background information!
dLeon last edited by dLeon
I wonder why Flash is preferred over HTML(5) by default
I believe it's not. Chromium/Chrome is always prefer HTML5 set, it's Google self policy. Youtube is really a good example. It won't bother to even check Flash plugin exist if it could detect at least one of supported Video container by HTML5. If all fail, then they drop to Flash.
With exception, the site coded to use Flash by default. And there's still a lot, nowadays. :grin:
Just check people post with Flash problem with some sites around this forum.
The merge like @xyzzy mentioned above just cause annoying effect. Now, everybody know Flash plugin must/should be exist in your browser. Best bet you just don't allow it to auto play.
The old way disabling plugin in plugin page is same like telling anyone; no, there is not that plugin in here, dude.