Google Chrome: Build 61.0.3163.79 with support for WebUSB

Google is now distributed in the stable channel, so for all users, Chrome in the new version 61.0.3163.79. According to the company, the new build will now be rolled out and will reach all Windows, Mac and Linux users in steps in the next days and weeks. I have already received the update directly via the update function of the browser. In addition to some features, the new build contains numerous bug fixes and / or closes some security holes.

For example, some specific problems were fixed with PDFium, an open-source rendering engine for PDF files. On the top, you as normal users but the optimizations probably not so much received. However, many developers are pleased, because Google rewards rewards to those who had tracked and narrowed the errors – up to $ 5,000.

It is probably more interesting for you that Chrome generally supports the version 61 WebUSB and JavaScript modules. Through the WebUSB API, web apps can now access USB devices when the user allows them. The JavaScript modules, in turn, make the work easier for developers. For developers, Google has also introduced a whole series of optimizations, which summarize the colleagues of The Verge:

  • The Network Information API is now available on the desktop as well as
  • Creators can now specify scrolling smoothness via a new optional parameter in existing Scroll APIs or with the scroll-behavior CSS property.

    The CSSOM View SmoothScroll API provides native smooth scrolling to the platform through a scroll-behavior: smooth CSS property or by using the window.scrollTo () DOM scroll method, eliminating the need to implement this behavior with JavaScript


    CSS color values ​​can now be 8- and 4-digit hex colors of the format #RRGGBBAA and #RGBA

    Sites can now access the relative positions of the screen content with the VisualViewport API, exposing complex functionality like pinch and zoom in a more direct way.

    The device RAM API is now available, exposing the amount of RAM on a web application.

    If you want to use a custom Chrome tab,

    For video using nativecontrols, Chrome will now automatically redate its device in an orientation that matches a video playing on the screen

  • nextHopProtocol is now available in Resource Timing and Navigation
  • Sites can now require embedded third-party content to enforce a given content Security policy via the new csp attribute on iframe width = "300" height = "150" elements

    The DOMTokenList interface now is a replacement to a new one.

    To get a list of attribute names of an element, getAttributeNames () is now supported and gives developers a more direct mechanism than going through the attributes collection

    To increase security, sites will now automatically exit fullscreen if a JavaScript dialog opens.

  • API's new () function
  • The URLSearchParams constructor has been updated to accept any URLSourceParams instances.

The URLSearchParams constructor has been updated to accept any URLSearchParams instances

To prevent the use of mis-certificates from going unnoticed, sites can use the new Expect-CT HTTP header that will enable automatic reporting and / or enforcement of Certificate Transparency requirements

Chrome will not decode any decoding frames for videos using MediaSource in background tabs

"Non-Live" camera settings can be used as photo resolution, red eye reduction, and flashmode can be retrieved with ImageCapture.getPhotoSettings ().

  • Site can now use the Clear-Site-Data header to delete its own client-sidedata, search as cookies, serviceworkers, storage, and cache entries.
  • In addition, google itself also in several contributions on the changes in the developer tools. Richly readable, which is for you so standard users but of course in the daily life does not necessarily play the biggest role. Have you already got the update on Chrome 61.0.3163.79 already? With me it is already under Windows 10 already for the 64-bit version.