Stories
Slash Boxes
Comments

SoylentNews is people

posted by cmn32480 on Friday August 12 2016, @09:31AM   Printer-friendly
from the take-it-out-back-and-shoot-it dept.

Arthur T Knackerbracket has found the following story:

By the end of the year, Google Chrome will block virtually all Flash content and make whatever's left click-to-play by default.

In September, Chrome 53 will kill off all background Flash content, which is about 90 per cent of Flash on the web, according to Google.

Then in December, Chrome 55 will use HTML5 for video, animations, games and similar stuff. If there is no HTML5 available and instead just Flash, you'll be asked to explicitly enable the Adobe plugin to view it.

This will pile immense pressure on web developers to use HTML5 and ditch Flash, because Chrome will deliberately stall the plugin's user experience.

It's effectively throwing Flash out into the cold winter's night. There is no more room at the inn. Google says it prefers HTML5 because it's faster to load than Flash and easier on handhelds' batteries. But the elephant in the room is Flash's dreadful security record: it is a screen door that lets the sewage of the internet seep in and infect computers.

Any Soylentils still have Flash installed on their systems? What keeps you from removing it?


Original Submission

 
This discussion has been archived. No new comments can be posted.
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: 0) by Anonymous Coward on Friday August 12 2016, @01:09PM

    by Anonymous Coward on Friday August 12 2016, @01:09PM (#386992)

    Youtube is not the only video website in the world.

  • (Score: 1, Informative) by Anonymous Coward on Friday August 12 2016, @07:15PM

    by Anonymous Coward on Friday August 12 2016, @07:15PM (#387135)

    Pale Moon [palemoon.org] (the Firefox-derived non-stupid browser) recently added some about:config options to allow users to force their autoplay preferences over pages containing HTML5 video served by remote sites such as youtube.

    I believe the new key piece was "media.autoplay.allowscripted", to supplement the existing "media.autoplay.enabled", except that the former does what most humans expected the latter to do. Set them both to "disabled" and HTML5 sites never autoplay media.