Chrome 61 Arrives With JavaScript Modules, WebUSB Support (venturebeat.com)
The latest version of Google Chrome has launched, bringing a host of new developer features like JavaScript modules and WebUSB support. An anonymous Slashdot reader shares a report from VentureBeat: Google has launched Chrome 61 for Windows, Mac, and Linux. Additions in this release include JavaScript modules and WebUSB support, among other developer features. You can update to the latest version now using the browser's built-in silent updater or download it directly from google.com/chrome. Google also released Chrome 61 for Android today. In addition to performance and stability fixes, you can expect two new features: Translate pages with a more compact toolbar and pick images with an improved image picker.
Chrome now supports JavaScript modules natively via the new element, letting developers declare a script's dependencies. Modules are already popular in third-party build tools, which use them to bundle only the required scripts. Native support means the browser can fetch granular dependencies in parallel, taking advantage of caching, avoiding duplications across the page, and ensuring the script executes in the correct order, all without a build step. Google recommends these two blog posts for more information: ECMAScript modules in browsers and ES6 Modules in Depth. Speaking of JavaScript, Chrome 61 also upgrades the browser's V8 JavaScript engine to version 6.1. Developers can expect performance improvements and a binary size reduction. The WebUSB API meanwhile allows web apps to access user-permitted USB devices. This enables all the functionality provided by hardware peripherals such as keyboards, mice, printers, and gamepads, while still preserving the security guarantees of the web.
Chrome now supports JavaScript modules natively via the new element, letting developers declare a script's dependencies. Modules are already popular in third-party build tools, which use them to bundle only the required scripts. Native support means the browser can fetch granular dependencies in parallel, taking advantage of caching, avoiding duplications across the page, and ensuring the script executes in the correct order, all without a build step. Google recommends these two blog posts for more information: ECMAScript modules in browsers and ES6 Modules in Depth. Speaking of JavaScript, Chrome 61 also upgrades the browser's V8 JavaScript engine to version 6.1. Developers can expect performance improvements and a binary size reduction. The WebUSB API meanwhile allows web apps to access user-permitted USB devices. This enables all the functionality provided by hardware peripherals such as keyboards, mice, printers, and gamepads, while still preserving the security guarantees of the web.
while still preserving the security guarantees of the web.
I would've stopped reading right there.
you mean a zero day to follow ?!!
you mean unintentional (wink) programming flaws that leak user info?
i guess me and the other 5 people on the planet still worried about security will not be installing it. good luck the world.
This JavaScript bullshit has gone too far. It's features are already abused too much, this will just make things worse.
Anons need not reply. Questions end with a question mark.
HOLY FUCK! I've read one of the articles, and it mentions some stuff that I find really, really, really fucking creepy.
HOLY FUCK! I don't want my browser to be able to give web sites access to that info!
HOLY FUCK! I don't want my browser to be able to give web sites access to that info!
HOLY FUCK! I don't want my browser to be able to give web sites access to that info!
HOLY FUCK! I don't want my browser to be able to give web sites access to do that!
HOLY FUCK! I don't want this stuff!
I'm hoping that the next version of Chrome will allow web pages to automatically update my BIOS. It would be really useful for sysadmins and OEMs!
HOLY FUCK! I don't want my browser to be able to give web sites access to that info!
Then click No when the browser asks you if a particular origin should be able to use a particular API. Depending on localization decisions made before launch, the No button may be labeled Deny or Block or Don't Allow.
I think they are just being honest. "We have as much security as the wide open internet." Hopefully systemd has a method for blocking USB device access to a specific application, in this case chrome.
Had to block chrome from using dbus because it kept the computer from sleeping even with a blank page open. Chrome is bad at cleaning up it's dbus power manager locks.
Counting down to the first malware strain that sends advertisements to a 3D printer via WebUSB without users intervention...
Inheritance is the sincerest form of nepotism.
Somewhere in an event log "shadyadnetworked wanted access to your 3D printer" - "auto-granted via WebUSB settings"
Inheritance is the sincerest form of nepotism.
issue 1) this was already available as of Chrome 60 (behind a flag)
issue 2) as of Chrome 62 (Canary), the modules were not (as yet) loading in the correct order.
The module loader still gets confused if the nesting is too deep (I have to manually order part of the loading).
issue 3) it's not a "new element". It is new attributes on the same old element.
Seriously, don't go with what VentureBeat says about anything technical. As if they would even have a clue.