Firefox 69 Will Disable Adobe Flash Plugin by Default (zdnet.com)

Mozilla will take the next major step in disabling support for the Adobe Flash plugin later this year when it releases Firefox 69. From a report: Firefox 69 will be Mozilla's third last step to completely dropping support for the historically buggy plugin, which will reach end of life on December 31, 2020. Flash is the last remaining NPAPI plugin that Firefox supports. Mozilla flagged the change, spotted by Ghacks, in a new bug report that notes "we'll disable Flash by default in Nightly 69 and let that roll out". Firefox 69 stable will be released in early September, according to Mozilla's release calendar.

Comments

Version 69 "decouples" two things

[xxxJonBoyxxx]

Not exactly what the Internet would have expected.

User choice

[imidan]

This is a good step. It's great that browser makers are generally not beholden to people like advertisers for money, so they can make more user-friendly decisions. I'd like to see more, though.

I don't want autoplay anything in my browser. Especially audio and video. I use a plugin that aims to disable a lot of autoplay, but it doesn't always work. Why not have a browser flag that tells sites "I don't want autoplaying multimedia content"? I know crappy sites with video ads would ignore it, but more legitimate sites could respect it, potentially allowing them to save on bandwidth by not sending content to me that I don't want. I know I can stop it all by turning off JS entirely, but it's so integrated into so much of the web now that even simple sites barely work without it.

It's a little different from "do not track" in that even legitimate sites have monetary incentive to track me regardless of how I set that flag. What incentive do they have to stream videos to me that I don't want to watch?

Maybe I'm just in the minority in not wanting everything to be a video. Maybe the issue is that the sites have no motivation to obey "no autoplay" because it would cost developer time to satisfy a very small group of visitors.

Re:User choice

[markdavis]

>"Maybe I'm just in the minority in not wanting everything to be a video. [...] I don't want autoplay anything in my browser."

You might be in the minority, but you are FAR from alone. I *detest* ANY type of media autoplay- regardless of the type or if it is muted or not. And I think most users are very annoyed by any type of autoplay, but perhaps not motivated enough to fight it (especially if muted). Firefox is the only browser (I know of) so far that allows blocking autoplay of muted video (and no addon/plugin needed):

media.autoplay.default=1
media.autoplay.enabled.user-gestures-needed=false
media.autoplay.allow-muted=false

Although it will break some sites (I find in practice it is a rare thing, though). The Firefox UI currently includes no way to set the first two of the above, you must use about:config.

>"Maybe the issue is that the sites have no motivation to obey "no autoplay" because it would cost developer time to satisfy a very small group of visitors."

Or they are so arrogant and controlling they want to FORCE their crap down your throat regardless of your preferences, requests, or situation. I don't want my browsing experience to ever be like DVR-less "TV" or "Radio".

Re:Where now?

[RickyShade]

Use oldversion.com, put an alternate browser install to run along next to your main one.

Re: Flash

[sound vision]

It's actually not bad for making vector-based animations with interactive components. I believe that was its intended purpose. The issues came when people started using it to design entire web sites.

Re:What about when we need Flash?

[thegarbz]

Isolated virtual machine running Windows XP behind 3 firewalls installed only in RAM, and when you're done throw out the RAM sticks. Alternatively burn the building down. Safety first.