The inexorable slide into a world without Flash continues, with Google revealing plans to phase out support for Adobe's Flash Player in its Chrome browser for all but a handful of websites. And the company expects the changes to roll out by the fourth quarter of 2016.
While it says Flash might have "historically" been a good way to present rich media online, Google is now much more partial to HTML5, thanks to faster load times and lower power use.
As a result, Flash will still come bundled with Chrome, but "its presence will not be advertised by default." Where the Flash Player is the only option for viewing content on a site, users will need to actively switch it on for individual sites. Enterprise Chrome users will also have the option of switching Flash off altogether.
Google will maintain support in the short-term for the top 10 domains using the player, including YouTube, Facebook, Yahoo, Twitch and Amazon. But this "whitelist" is set to be periodically reviewed, with sites removed if they no longer warrant an exception, and the exemption list will expire after a year.
A spokesperson for Adobe said it was working with Google in its goal of "an industry-wide transition to Open Web standards," including the adoption of HTML5.
"At the same time, given that Flash continues to be used in areas such as education, web gaming and premium video, the responsible thing for Adobe to do is to continue to support Flash with updates and fixes, as we help the industry transition," Adobe said in an emailed statement. "Looking ahead, we encourage content creators to build with new web standards."
Protect your synced data - Chrome Help - 0 views
When you sign in to Chrome and enable sync, Chrome keeps your information secure by using your Google Account credentials to encrypt your synced passwords. Alternatively, you can choose to encrypt all of your synced data with a sync passphrase. This sync passphrase is stored on your computer and isn't sent to Google.
- Click the Chrome menu on the browser toolbar.
- Select Signed in as <your email address> (you must be signed in to Chrome already).
- In the "Sign in" section, click Advanced sync settings.
- Choose an encryption option:
- Encrypt synced passwords with your Google credentials: This is the default option. Your saved passwords are encrypted on Google's servers and protected with your Google Account credentials.
- Encrypt all synced data with your own sync passphrase: Select this if you'd like to encrypt all the data you've chosen to sync. You can provide your own passphrase that will only be stored on your computer.
- Click OK.
Months of work on "chromoting" have reached fruition with Google's release on Friday of a new Chrome extension to let a person on one computer remotely control another across the network.
The Chrome Remote Desktop beta version, which arrived Friday, is a browser-based equivalent of remote desktop software for conventional operating systems. Such software is handy for IT administrators managing employees' machines, people taking care of their relatives' computers, or individuals getting access to their own machines from afar.
Google is phasing out the internal use of Microsoft’s ubiquitous Windows operating system because of security concerns, according to several Google employees.
The directive to move to other operating systems began in earnest in January, after Google’s Chinese operations were hacked, and could effectively end the use of Windows at Google, which employs more than 10,000 workers internationally.
Employees said it was also an effort to run the company on Google’s own products, including its forthcoming Chrome OS, which will compete with Windows. “A lot of it is an effort to run things on Google product,” the employee said. “They want to run things on Chrome.”
The traditional browser plug-in model has enabled tremendous innovation on the web, but it also presents challenges for both plug-ins and browsers. The browser plug-in interface is loosely specified, limited in capability and varies across browsers and operating systems. This can lead to incompatibilities, reduction in performance and some security headaches.
That’s why we are working with Adobe, Mozilla and the broader community to help define the next generation browser plug-in API. This new API aims to address the shortcomings of the current browser plug-in model. There is much to do and we’re eager to get started.
As a first step, we’ve begun collaborating with Adobe to improve the Flash Player experience in Google Chrome. Today, we’re making available an initial integration of Flash Player with Chrome in the developer channel. We plan to bring this functionality to all Chrome users as quickly as we can.
We believe this initiative will help our users in the following ways:
- When users download Chrome, they will also receive the latest version of Adobe Flash Player. There will be no need to install Flash Player separately.
- Users will automatically receive updates related to Flash Player using Google Chrome’s auto-update mechanism. This eliminates the need to manually download separate updates and reduces the security risk of using outdated versions.
- With Adobe's help, we plan to further protect users by extending Chrome's “sandbox” to web pages with Flash content.
"We are excited that much of the technology in Gears, including offline support and geolocation APIs, are being incorporated into the HTML5 spec as an open standard supported across browsers, and see that as the logical next step for developers looking to include these features in their websites," wrote a Google spokesman in an e-mail.
That's great, but HTML5 isn't ready yet, and commercially available browsers don't support it.
Google upgraded the beta version of its Chrome browser yesterday, adding integrated bookmark synchronization and boasting of a 30% speed improvement over the current production edition.
Bookmark sync requires that all the machines being kept in step run the Chrome beta, and that the user has a Google account, such as a Gmail username and password. The browser syncs bookmarks using Google Docs, the company's Web-based application suite.
Good news for extension developers: as of today, extensions are turned on by default on Google Chrome's dev channel.
Extensions are small pieces of software that developers can write to customize the way Google Chrome works. We've been working on enabling extensions for a while, but until now, they were hidden behind a developer flag. As of today, this is no longer true. If you're on the dev channel, you can try installing some of our sample extensions.
Removing the flag is the first step in our launch process, and it means we're ready for a few more people to start using extensions-- the kind of adventurous people who populate the dev channel.