Chrome Platform Status - Features't allow popups during page unload2018-05-18T20:46:28ZChrome Platform,2018-05-18:/feature/5989473649164288/A web page can use the API to create popups or tabs. This is a highly abusable feature, so we have a system in place called the "popup blocker" to put strict limits on the use of this API. This would remove the ability of a page to use the API during page unload, whether or not the popup blocker is enabled. This would simplify browser shutdown and improve our ability to make it correct.Network Error Logging2018-05-18T18:09:24ZChrome Platform,2018-05-18:/feature/5391249376804864/Defines a mechanism that enables developers to declare a network error reporting policy for a web application. A user agent can use this policy to report encountered network errors that prevented it from successfully fetching requested resources.ServiceWorkerRegistration#updateViaCache and no-cache by default for main service worker scripts2018-05-18T06:33:37ZChrome Platform,2018-05-18:/feature/6059838387781632/ServiceWorkerRegistration#updateViaCache controls whether the browser cache (the HTTP cache) is consulted when performing a service worker update check. The default behavior also changes. Previously, the browser cache was consulted for all scripts by default. Now, it is skipped for the main script and consulted for imported scripts bv default.ReportingObserver. Deprecation Reports2018-05-17T19:18:14ZChrome Platform,2018-05-17:/feature/4691191559880704/These features are closely related to the previously proposed Reporting API ( Deprecation reports are one type of report be routed into the Reporting API backend. ReportingObserver is a new observer that will allow developers to observe reports from JavaScript. See this explainer ( for more details.Cross-Origin Read Blocking (CORB)2018-05-17T02:58:14ZChrome Platform,2018-05-17:/feature/5629709824032768/Cross-Origin Read Blocking (CORB) is an algorithm that can identify and block dubious cross-origin resource loads in web browsers before they reach the web page. CORB reduces the risk of leaking sensitive data by keeping it further from cross-origin web pages. In most browsers, it keeps such data out of untrusted script execution contexts. In browsers with Site Isolation, it can keep such data out of untrusted renderer processes entirely, helping even against side channel attacks like Spectre.RTCQuicTransport & RTCQuicStream2018-05-16T21:38:04ZChrome Platform,2018-05-16:/feature/6311472179183616/Implement the RTCQuicTransport and RTCQuicStream, a standalone API using the QUIC transport protocol to exchange arbitrary data with remote peers. This provides a generic multiple way transport that doesn't use the full PeerConnection stack designed for media purposes.RTCIceTransport2018-05-16T21:36:21ZChrome Platform,2018-05-16:/feature/6276032524976128/Implement the RTCIceTransport, a standalone network transport that allows application access to information about the ICE transport over which packets are exchanged. The ICE protocol manages peer-to-peer connections and is designed to work around issues that block these connections like NATs and firewalls using technologies such as STUN and TURN. This is defined in an extension specification that allows for construction without an offer/answer exchange using a WebRTC PeerConnection.Picture-in-Picture (PiP)2018-05-16T11:12:22ZChrome Platform,2018-05-16:/feature/5729206566649856/Allow websites to create a floating video window that is always on top of other windows so that users may continue consuming media while they interact with other sites or applications on their device.RTCConfiguration.iceCandidatePoolSize2018-05-15T19:44:39ZChrome Platform,2018-05-15:/feature/4973817285836800/Normally, ICE candidates are only gathered after RTCPeerConnection.setLocalDescription is called, because this is the point at which the PeerConnection knows how many ports it needs. The iceCandidatePoolSize member of RTCConfiguration instructs the PeerConnection to gather ICE candidates before this occurs, as a performance optimization. Thus, if setting the local description is delayed (by signaling, for example), interactions with STUN/TURN servers can occur in parallel.Stylesheets activated after the body is started do not block paint2018-05-15T14:19:22ZChrome Platform,2018-05-15:/feature/5696805480169472/External stylesheets in the body of the document or that get activated after the body has started to be parsed will no longer block paint but they will pause the parser. The end result is that any DOM content before the body stylesheet will continue to paint but content after the stylesheet will not appear until after the stylesheet has loaded.Slots in a flat tree2018-05-15T07:38:59ZChrome Platform,2018-05-15:/feature/5743296429162496/The <slot> element can now participate in a flat (layout) tree, with UA style: display: contents. Before this change, applying a CSS selector to a <slot> element had no effect. Not only is this fixed, when selectors are applied to a <slot> element, it's children inherit its styles.Background Tab Resource Load Throttling2018-05-14T19:49:10ZChrome Platform,2018-05-14:/feature/5527160148197376/In background tabs, the maximum number of active resource loading requests is limited. The limit can be different for the top frame, and other sub-frames. WebSockets, WebRTC's data channel, and Fetch API can be used beyond the limit. This feature is under experiments, and may be enabled on Chrome 66. From Chrome 68, XMLHttpRequest and EventSource can be too.Support 'x' as a resolution unit2018-05-12T16:07:31ZChrome Platform,2018-05-12:/feature/5150549246738432/In, 'x' is defined as a synonym for dppx. Add support for parsing 'x' as dots per px.Add referrerpolicy support to <script> elements2018-05-12T04:48:11ZChrome Platform,2018-05-12:/feature/5227651627220992/Many resource-fetching elements have support for the `referrerpolicy` attribute, which lets developers provide a keyword to influence the value of the `Referer` HTTP header that accompanies a request. The <link> element has support for this, so it is possible to fetch a script with a developer-set referrer policy with <link rel=preload as=script referrerpolicy=... href=...>. The script element currently does not have support for the referrerpolicy attribute, and this feature adds support for it.Unified touch adjustment2018-05-11T18:48:36ZChrome Platform,2018-05-11:/feature/4895751150764032/Touch adjustment will adjust TouchEvent and also corresponding PointerEvent target to a best target within the touch area. TouchEvent coordinates will not be changed.