Close ad

Google is going to fight autoplay videos even more in the next versions of its popular Chrome browser. They will not start playing again until you open the corresponding tab. So there will be no more unexpected playback in the background. Starting in September, Chrome will also block most Flash ads.

About changing access to autoplay videos informed on Google+ developer François Beaufort, saying that while Chrome will always load a video as of now, it won't start playing until you're looking at it. The result will be battery saving, but above all it will ensure that you will no longer be surprised where something started playing in the background.

From September 1, Google is preparing block most flash ads for better performance. Ads that run on the AdWords platform will be automatically converted to HTML5 to continue to appear in Chrome, and Google recommends everyone else take the same step – converting from Flash to HTML5.

This is certainly positive news for users, however, Google has not yet decided to take a bolder step, which would be the complete removal of Flash in Chrome, following the example of iOS or Android.

Advertisements are a major source of revenue for Google, so it's not too surprising that the other activity it's been developing recently. Google engineers have started sending out code to developers that they can use to bypass the latest security measures that Apple is planning in iOS 9.

In iOS 9, which should be released to the public in a few weeks, a new security element App Transport Security (ATS) appeared, which requires the use of HTTPS encryption after all incoming content to the iPhone. This condition then ensures that none of the third parties can track what people are doing on their devices.

However, not all current advertising solutions use HTTPS, so in order for these ads to be displayed in iOS 9, Google sends out the mentioned code. This is nothing illegal, but certainly not something that Apple should be happy about. After all, Google is not bypassing security features in a similar way for the first time - in 2012 he had to pay 22,5 million dollars for not following the security settings in Safari.

Source: The Verge, Cult of Mac
.