Chrome Platform Status - Featureshttp://www.chromestatus.com/features2019-02-15T20:57:54ZDeprecate PaymentAddress.languageCode2019-02-15T20:57:54ZChrome Platform Statustag:www.chromestatus.com,2019-02-15:/feature/4992562146312192/PaymentAddress.languageCode is browser's best guess for the language of the text in the shipping, billing, delivery, or pickup address in Payment Request API. The languageCode is marked at risk in the spec and has already been removed from Firefox and Safari. Usage in Chrome is small enough for safe removal. Removal is expected in Chrome 74.File Handling2019-02-15T16:49:57ZChrome Platform Statustag:www.chromestatus.com,2019-02-15:/feature/5721776357113856/File Handling provides a way for web applications to declare the ability to handle files with given MIME types and extensions. The web application will receive an event when the user intends to open a file with that web application.inverted-colors media query2019-02-15T16:28:43ZChrome Platform Statustag:www.chromestatus.com,2019-02-15:/feature/5940010603773952/An indication that the user agent or underlying operating system has forcibly inverted all colors, not a request to do so. This is sometimes provided as a simple accessibility feature, allowing users to switch between light-on-dark and dark-on-light text.Accessible Object Model (AOM)2019-02-15T16:27:25ZChrome Platform Statustag:www.chromestatus.com,2019-02-15:/feature/6643371200217088/This effort aims to create a JavaScript API to allow developers to modify (and eventually explore) the accessibility tree for an HTML page.ARIA 1.12019-02-15T16:25:47ZChrome Platform Statustag:www.chromestatus.com,2019-02-15:/feature/5761503818940416/Implement the changes in version 1.1 of the Accessible Rich Internet Applications (WAI-ARIA) 1.1 spec.KV storage2019-02-15T16:02:22ZChrome Platform Statustag:www.chromestatus.com,2019-02-15:/feature/6428344899862528/KV storage provides a simple, asynchronous key/value store with a modern API. Additionally, it allows easy creation of isolated storage areas beyond the default one. KV storage is layered on top of IndexedDB, storing its data in a specific database, so the developer can fall back to using IndexedDB directly when necessary.Feature Policy: Autoplay2019-02-15T16:02:04ZChrome Platform Statustag:www.chromestatus.com,2019-02-15:/feature/5100524789563392/Allows developers to selectively enable and disable use of autoplay through the feature policy HTTP header or the <iframe> "allow" attribute. By default we will allow autoplay on same origin iframes. If developers have cross origin iframes they will be able to enable autoplay on those frames by enabling the "autoplay" feature.Origin-Signed HTTP Exchanges2019-02-15T04:21:01ZChrome Platform Statustag:www.chromestatus.com,2019-02-15:/feature/5745285984681984/Allows sites to send HTTP request/response pairs (exchanges) that are authoritative for an origin, even when the server itself is not authoritative for that origin. This is part of Web Packaging, which will allow people to share web applications peer-to-peer, while offline, with proof that an app comes from its original author. This also shares some infrastructure with signature-based SRI.Deprecate opener navigation downloads from cross origin popups 2019-02-14T19:24:59ZChrome Platform Statustag:www.chromestatus.com,2019-02-14:/feature/5742188281462784/If a popup navigates its opener to a URL which results in a download, the download will be blocked and the navigation cancelled, if the popup is cross-origin to its opener. This resolves a long standing security issue.Remove Insecure Usage of DeviceOrientationEvent2019-02-14T12:35:48ZChrome Platform Statustag:www.chromestatus.com,2019-02-14:/feature/5468407470227456/Chromium has been showing deprecation warnings since 2015 whenever the API is used in a non-secure browsing context. It is time to actually restrict these APIs to secure browsing contexts. This change brings Chromium’s implementations in line with the privacy and security recommendations in the spec, and is aligned with the overarching effort to deprecate powerful features on insecure origins.Remove Insecure Usage of DeviceMotionEvent2019-02-14T12:35:35ZChrome Platform Statustag:www.chromestatus.com,2019-02-14:/feature/5688035094036480/Chromium has been showing deprecation warnings since 2015 whenever the API is used in a non-secure browsing context. It is time to actually restrict these APIs to secure browsing contexts. This change brings Chromium’s implementations in line with the privacy and security recommendations in the spec, and is aligned with the overarching effort to deprecate powerful features on insecure origins.Remove [NoInterfaceObject] from DeviceOrientation Event interfaces2019-02-13T20:58:57ZChrome Platform Statustag:www.chromestatus.com,2019-02-13:/feature/5981148249325568/The [NoInterfaceObject] annotation is being removed from WebIDL. The DeviceOrientation Event specification has been updated to remove this annotation from the Acceleration and RotationRate interfaces and rename them to DeviceMotionEventAcceleration and DeviceMotionEventRotationRate in order to avoid polluting the global namespace with generic interface names.Remove [NoInterfaceObject] from Geolocation API interfaces2019-02-13T20:58:51ZChrome Platform Statustag:www.chromestatus.com,2019-02-13:/feature/5172722929762304/The [NoInterfaceObject] annotation is being removed from WebIDL. The Geolocation API specification has been updated to remove this annotation from all interfaces and perform the following renames to avoid polluting the global namespace with generic interface names, Geolocation -> NavigatorGeolocation Coordinates -> NavigatorGeolocationCoordinates Position -> NavigatorGeolocationPosition PositionError -> NavigatorGeolocationPositionErrorThrow on invalid "basic-card" data2019-02-13T18:50:56ZChrome Platform Statustag:www.chromestatus.com,2019-02-13:/feature/4793925806063616/If invalid "supportedNetworks" or "supportedTypes" are specified for "basic-card" payment, then the PaymentRequest constructor should throw a TypeError.User Activation Delegation through postMessages2019-02-12T21:26:43ZChrome Platform Statustag:www.chromestatus.com,2019-02-12:/feature/5574000088449024/This feature allows transferring user activation from one frame to another through postMessages(). User interaction in a frame activates the frame as well as all its ancestor (container) frames by default. See https://www.chromestatus.com/feature/5722065667620864. Here we are adding an option to postMessage() to allow an activated frame to relinquish the activation and pass it on a non-ancestor frame.