4 ms·

Wait, what's this about re-enabling flash? From what I heard, Chrome 56 is going to disable flash by default.

• cpeterso 10y ago
  Chrome 56 is supposed to make Flash click-to-play on sites that the user doesn't frequent ("site engagement"). The engagement threshold will ramp up through 2017 until Flash is click-to-play by default on all sites.
  • 0x0 10y ago
    I used to disable flash in chrome://plugins/ but starting in Chrome 56 it keeps re-enabling it there (and all the other plugins) on every launch. I still have "click-to-play-flash" set, but the result is that instead of being served a html5 player, I'm being served a blocked "click-to-play" flash player.
    • beojan 10y ago
      I have a feeling this is a bug rather than a deliberate choice, given Google are trying to encourage use of HTML5.
      • mynameisvlad 10y ago
        That, plus the "(and all the other plugins)" really signals that this is unintended. Something probably isn't reading or writing the setting to the right place, and it's just being enabled by default.
    • cpeterso 10y ago
      I just updated from Chrome 55 to 56 and saw the same thing in chrome://plugins. I guess Google's position is that click-to-play Flash is the same as disabled Flash because the plugin doesn't run without user action.