Chrome 53: Shadow DOM v1, Payment Request API and more
[To stay ahead of the game, subscribe to Chrome beta posts on http://blog.chromium.org/]
With Chrome 53, you can now easily create encapsulated, re-usable web components with Shadow DOM v1; mobile payments become streamlined with the Payments Request API; the Web Bluetooth API is available experimentally on some platforms as an origin trial and there’s plenty more.
Shadow DOM v1
Payment Request API
Completing payments on the web can be a cumbersome process for users, leading to lower conversions on sites. While autofill has made it easier to enter information, efficient data entry on mobile is still a challenge. PaymentRequest allows for fast, seamless, and secure payments on the web using a credit card or Android Pay. It also lets users provide a billing address, shipping details, and payer information without typing. PaymentRequest is available on Chrome for Android, with support for more platforms coming soon.
Video is a great way for sites to reach their users, but it can be jarring when it plays unexpectedly. This is especially true on mobile, where the user may be in an environment where audio is unwanted. Chrome on Android now allows muted videos to begin playing without user interaction. 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. Developers can also use script to play muted videos without user interaction. Muted videos that begin playing sound before a user action will automatically be paused.
Sites that send notifications to Android devices running Android 6.0 (Marshmallow) or later may now provide a badge to show in the status bar in place of the Chrome logo.
Originally posted from http://youtu.be/FajnnR-9mhE