Skip to main content

Adobe Flash blocked by default for all users in the latest version of Chrome

Chrome 56: Web Bluetooth, CSS Position Sticky, and HTML5 By Default
The latest version of Google’s Chrome browser is out and it arrives with the company’s move to disable Adobe Flash Player by default when visiting web pages. Google warned about this feature last August, stating that using HTML5 by default not only creates a safer web browsing experience but is more power efficient too. The Flash-blocking feature recently appeared in the beta version of Chrome 56 and is now available to the masses in this new stable version.

“Today, more than 90 percent of Flash on the web loads behind the scenes to support things like page analytics. This kind of Flash slows you down,” Google said last August. “HTML5 is much lighter and faster, and publishers are switching over to speed up page loading and save you more battery life.”

Google began addressing Flash-based content in September with the release of Chrome 42. The update locked down some Flash content, requiring Chrome users to click on the Flash object to activate. The move to disable Flash content altogether actually arrived in the final version of Chrome 55 released in December but the feature was only available to one percent of its users.

According to Google, the new HTML5 by default feature will disable all Flash content on a website unless the visitor specifies otherwise, meaning Chrome users can allow the browser to play Flash on sites they trust and visit frequently. Otherwise, Flash content will require the user’s permission to play on sites they are visiting for the first time.

“Flash prompting will only be enabled for sites whose Site Engagement Index (SEI) is below a certain threshold,” Google states. “For Chrome 55, starting in January 2017 prompts will only appear for sites where the user’s SEI is less than one.  That threshold will increase to 100 through October 2017, when all Flash sites will require an initial prompt.”

In other words, by October, all websites will require Chrome users to initially give permission to run Flash-based content on their pages. Google previously said that just by pushing Flash-based content into click-to-play mode, Chrome users saw “an immediate positive impact” due to faster page loads and reduced power consumption.

In addition to the new HTML5 by default feature, Chrome 56 also signals the arrival of Bluetooth support for web-based apps. This is made possible by the new Web Bluetooth API that uses the GATT protocol to enable web apps to communicate with Bluetooth low-energy devices like LED displays, toys, light bulbs, and more. Adding Bluetooth support means developers can insert just “a few lines of JavaScript” to their web-based apps.

Chrome 56 also now fully supports WebGL 2.0. This is a means for rendering web-based 3D graphics within the browser window using graphics processors located inside PCs and mobile devices instead of their central processor. It’s similar to how DirectX works in desktop gaming in that developers can use the graphics chip to handle most of the work, only WebGL does this within the browser environment. Ultimately, Chrome users will see richer 3D games and other content with WebGL 2.0 than the previous version.

To manually update Chrome, click on the three-dot button to the right of the address bar, and then select “Help > About Google Chrome.” Otherwise, Google Chrome can be downloaded here.

Editors' Recommendations

Kevin Parrish
Former Digital Trends Contributor
Kevin started taking PCs apart in the 90s when Quake was on the way and his PC lacked the required components. Since then…
Google tries to scare Edge users away from installing Chrome extensions
Microsoft Edge logo.

Microsoft has been promoting its Edge browser as a faster and more modern version of the much-hated Internet Explorer, as it is based on the same Chromium architecture as Google Chrome. That also means that it supports Chrome extensions. However, Google is trying to warn Edge users away from the extensions in its Chrome Web Store.

First spotted by Windows Latest, Edge users see a banner at the top of the page when they view an extension in the Chrome Web Store. "Google recommends switching to Chrome to use extensions securely," it reads, followed by a link to download the Google Chrome browser.

Read more
Chrome is ditching third-party cookies because Google wants your data all to itself
chocolate chip cookies

In January, Google announced its Chrome browser would begin phasing out support for third-party cookies. Chrome is by far the most popular browser in the world, and its elimination of cookies will effectively kill off this key advertising and data-tracking tool for good.

While this looks like a win for privacy on some level, what happens next could end up being much worse for everyone’s privacy, said Elizabeth Renieris, a fellow at the Harvard Berkman Klein center and a data protection and privacy lawyer.

Read more
1.5% of Chrome users’ passwords are known to be compromised, according to Google
A password screen with an indecipherable password inputted.

1.5% of passwords used in Chrome are unsafe and have been released in data breaches, according to new information from Google.

In February, a new feature was introduced to the Google Chrome browser which checks whether users' passwords are secure. Password Checkup is a free download that scans a database of 4 million compromised passwords and informs users if their password is among them and they need to change it. The database of passwords is collated from known third-party data breaches and when a user enters their password, it is checked against the list.

Read more