Chrome Platform Status - Featureshttp://www.chromestatus.com/features2017-09-20T06:36:48ZJavaScript module import()2017-09-20T06:36:48ZChrome Platform Statustag:www.chromestatus.com,2017-09-20:/feature/5684934484164608/This JavaScript feature adds a "function-like" import() module loading syntactic form to JavaScript. The existing syntactic forms for importing modules are static declarations. However, it's also desirable to be able to dynamically load parts of a JavaScript application at runtime.Promise.prototype.finally2017-09-20T02:40:58ZChrome Platform Statustag:www.chromestatus.com,2017-09-20:/feature/5704570235781120/This finally method is used for registering a callback to be invoked when a promise is settled (either fulfilled, or rejected).Async Iteration / Async Generators2017-09-20T02:33:29ZChrome Platform Statustag:www.chromestatus.com,2017-09-20:/feature/5727385018171392/Async Generator functions and a new iteration protocol (used by for-await-of loops and yield* expressions), to streamline consumption or implementation of streaming data sources.WebAssembly SIMD2017-09-19T22:31:14ZChrome Platform Statustag:www.chromestatus.com,2017-09-19:/feature/6533147810332672/WebAssembly SIMD will expose hardware SIMD instructions to WebAssembly applications in a platform-independent way. Implementations will explore using SIMD.js as a basis for WebAssembly SIMD. Add three SIMD vector types: float32x4, float64x2, and int32x4, and corresponding Typed Array views. SIMD can speed up applications that process lots of data that is naturally organized as 2, 3, or 4 element vectors. SIMD is also useful when compiling native code to WebAssembly.Throw NotSupportedError when media playbackRate is unsupported2017-09-19T09:58:06ZChrome Platform Statustag:www.chromestatus.com,2017-09-19:/feature/5750156230131712/Throw a NotSupportedError DOM exception when a media element’s playbackRate is set to an unsupported value.Battery Status API2017-09-19T07:17:25ZChrome Platform Statustag:www.chromestatus.com,2017-09-19:/feature/4537134732017664/Allows access to see the battery level of the device's batteryIntl.NumberFormat.prototype.formatToParts()2017-09-18T23:25:08ZChrome Platform Statustag:www.chromestatus.com,2017-09-18:/feature/5686840812109824/Intl.NumberFormat.prototype.formatToParts() is scheduled to be added to the EcmaScript Internationalization API specification (Ecma 402). It adds a method to format a number to a list of tokens and their types (e.g. minusSign, integer, decimal, fraction, currency, percentSign, etc). It is implemented and disabled by default by Firefox. v8 implemented it behind a flag. See also, the corresponding DateTimeFormat feature here: https://www.chromestatus.com/feature/6319456309477376CSS: Support 'q' length unit2017-09-18T23:23:23ZChrome Platform Statustag:www.chromestatus.com,2017-09-18:/feature/5983903483428864/support 'q' absolute length unit. 1q is equivalent to 1/40th of 1cm.Trusted Types for DOM Manipulation2017-09-18T11:09:31ZChrome Platform Statustag:www.chromestatus.com,2017-09-18:/feature/5650088592408576/This feature introduces a number of types meant to capture the kinds of strings that developers wish to inject into a document via sinks such as `innerHTML`. These types might perform autoescaping, or might allow explicitly unsafe assignment. These new types in place, it adds variants of those setters and methods that accept the new types, and gives developers ways of locking themselves out of using the `DOMString` variants.Loosen up escape sequence restrictions in template literals2017-09-18T06:58:04ZChrome Platform Statustag:www.chromestatus.com,2017-09-18:/feature/4588025757564928/The restriction on escape sequences in template literals has been loosened. This enables new use cases for template tags, such as writing a LaTeX processor.createElementNS() : Throw InvalidCharacterError instead of NamespaceError on validating a qualified name2017-09-18T02:33:56ZChrome Platform Statustag:www.chromestatus.com,2017-09-18:/feature/5918678717562880/createElementNS() should now throw only InvalidCharacterError, not NamespaceError. Validating a qualified name should only throw InvalidCharacterError, not NamespaceError, after: https://github.com/whatwg/dom/issues/319 https://github.com/w3c/web-platform-tests/issues/5161 https://github.com/whatwg/dom/issues/423 Latest spec: https://dom.spec.whatwg.org/#validateDevice Memory JS API2017-09-17T23:55:35ZChrome Platform Statustag:www.chromestatus.com,2017-09-17:/feature/5119701235531776/JS API to expose the device Memory to web applications.IndexedDB: webkitGetDatabaseNames2017-09-17T10:51:24ZChrome Platform Statustag:www.chromestatus.com,2017-09-17:/feature/5725741740195840/The API asynchronously returns a list of existing database names in an origin, which seemed sensible enough. The design is flawed, in that the results may be obsolete as soon as they are returned, so it can really only be used for logging, not serious application logic. Not implemented in other browsers. https://github.com/w3c/IndexedDB/issues/31 tracks/links to previous discussion on flaws and possible alternatives.ClipboardEvent Constructor2017-09-17T10:45:43ZChrome Platform Statustag:www.chromestatus.com,2017-09-17:/feature/4687833935642624/This entry tracks exposing ClipboardEvent constructor. Remove FileReaderSync from service workers2017-09-17T10:36:35ZChrome Platform Statustag:www.chromestatus.com,2017-09-17:/feature/5739144722513920/The Service Worker spec has always had the (non-normative) note that "any type of synchronous requests must not be initiated inside of a service worker", to avoid blocking the service worker (as blocking the service worker would block all network requests from controlled pages). However synchronous APIs such as FileReaderSync were still available in service workers. So we'd like to fix that by removing this API from service workers. This was deprecated in Chrome 57.