Chrome for Android Adds Shadow DOM, PaymentRequest, Faster Video Playback

Chrome on Android plays videos auto and faster, smoother videos, less battery usage, gets new Shadow DOM, PaymentRequest.

Share online:

Video playback on Google's mobile browiser Chrome 52 on Android has become smoother, videos now loads faster, and the battery consumption is gone down.

"This means you will see smoother playback and faster load times. Videos will now start playing sooner, instead of pausing briefly before loading, and your battery will last longer," Google said.

These improvements are most noticeable on short videos, and with more publishers and sites moving to HTML5, video experience on Chrome will just keep getting better.

In addition, video also now works with 'Data Saver Mode,' saving you as much as 50% on data by showing a lightweight version of the video.

While at it, Chrome 53 Beta release today adds Shadow DOM, PaymentRequest, and Android autoplay.

Here's how these new features helping you:

Shadow DOM V1, allows an element to encapsulate its style and child DOM away from the main document, and improves the maintainability of large or composed sites.

Chrome for now support both v0 7 v1 versions of the API until enough developers have moved to V1.

PaymentRequest allows faster, seamless, and secure payments on the web using a credit card or Android Pay. Additonally, it also allows users to provide a billing address, shipping details, and payer information without typing.

It's is available on Chrome for Android, with support for more platforms coming soon.

Chrome on Android now 'autoplays muted video' —meaning no user interaction is required. "If the video was marked as muted and has the autoplay attribute, Chrome will start playing the video when it becomes visible to the user," explains Google. Muted videos that begin playing sound before a user action will automatically be paused.

In additon, developers can also use script to play muted videos without user interaction.

You can check for other new features and deprecations and interoperability improvements in this release, over here.

Unless otherwise noted, these new features are released to Chrome Beta channel release for Android, Chrome OS, Linux, Mac, and Windows.

Video is a great way for sites to reach their users, web video is huge, with over a billion hours played in Chrome every week on sites like Amazon, Facebook, The New York Times, Netflix and YouTube.

In another post earlier in July, Google advised publishers to embed video as they are one of the most engaging formats for content consumption.

According to Hubspot, online video now accounts for 50% of all mobile traffic.

Publishers can incorporate videos into their content in two ways:

  • "Create, share and then embed your own original video content onto your site.
  • Embed public video content onto your site."

Google explains that while the first option may lead to greater revenue for your site through the use of pre-roll, mid-roll or post-roll ads, —but it requires an upfront investment to create original video content.

But, embedding public videos onto your site content is a better option—becasue, this strategy lets publishers focus on curating high quality video content rather than spending time and resources on creating ithemselves.

However, publishers embedding public videos into their original content must ensure that the videos themselves do not violate any policies.

Whichever strategy you choose, embed video content onto your site that matters the most.

Publisher can easily embed videos on their content publishing software easily by using either an iframe tag, or an object tag—as both tags are provided by YouTube and other video hosting sites.

<code>iframe</code> today is the most preferable option as it offers more customizable options <code>object</code> is pass-now. You can for example, automatically play videos when the page loads or choose a specific video size to match the UX of your site.

For WordPress 3.x onwards, the developers for security reasons have restricted directly embedding an <code><iframe>....&lt;/iframe&gt;&lt;code&gt; tag, can use either a iframe plugin or use …. shortcode.

To learn how to correctly embed public videos please read the AdSense Program Policies.

Finally, Google had also recentlly added YouTube to HTTPS transparency report.

In the past two years, they company has steadily rolled out encryption using HTTPS to 97 percent of YouTube's traffic. "HTTPS provides critical security and data integrity for the web and for all web users."

In addition, Google has also began using HTTP Secure Transport Security (HSTS) on youtube.com that help cut down on HTTP to HTTPS redirects.

HSTS lifetime is one year as of now, but Google hope to preload this soon in web browsers. This improves both security and latency for end users.