Chrome 66

Enabled (34) | Origin Trial (0) | Behind a flag (0) | Deprecated (0) | Removed (0)

Enabled by default in 66

This release of Chrome had 34 new features.

Add and update MHTML headers to support sharing of MHTML pages

To support sharing of MHTML pages, a new header Snapshot-Content-Location will be added. The existing Subject header will be updated to support encoding of non-printable ASCII characters. #

This feature was specified in this Spec.

Resources

Docs: https://discourse.wicg.io/t/mhtml-generation-and-loading-as-implemented-in-chrome/2387

No linked samples

Add autocomplete attribute to and <select></h3> <p>Add autocomplete attribute to <textarea> and <select> as per spec. https://html.spec.whatwg.org/multipage/form-elements.html#the-select-element, https://html.spec.whatwg.org/multipage/form-elements.html#the-textarea-element <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=758078>#</a></p> <p>This feature was specified <a href=https://html.spec.whatwg.org/multipage/form-elements.html#the-select-element>in this Spec</a>.</p> <h3>Aligning U2F attestation with webauthn</h3> <p>Chrome has never supported the FIDO U2F API directly[1]. However, it does ship with an internal extension and it's possible to implement the U2F API by using postMessage to send messages to this extension. (Description continued in comments.) [1] https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-u2f-javascript-api-v1.2-ps-20170411.html <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=793985>#</a></p> <p>This feature was specified <a href=>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://www.chromium.org/security-keys>https://www.chromium.org/security-keys</a></p></p> No linked samples</p><h3>Array.prototype.values</h3> <p>The values() method returns a new Array Iterator object that contains the values for each index in the array. var <a href=https://bugs.chromium.org/p/v8/issues/detail?id=4247>#</a></p> <p>This feature was specified <a href=https://tc39.github.io/ecma262/#sec-array.prototype.values>in this Spec</a>.</p> <h4>Resources</h4> No linked docs</p> <p>Samples: <a href=https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/values>https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/values</a></p></p><h3>Asynchronous Clipboard API</h3> <p>A modern, asynchronous Clipboard API based on Promises. Text-only APIs (clipboard.readText and clipboard.writeText): * Behind a flag in M62 * Enabled by default in M66 Support for images and other data types is still under development. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=677564>#</a></p> <p>This feature was specified <a href=https://w3c.github.io/clipboard-apis/>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://web.dev/async-clipboard/>https://web.dev/async-clipboard/</a></p></p> <p>Samples: <a href=https://googlechrome.github.io/samples/async-clipboard/>https://googlechrome.github.io/samples/async-clipboard/</a></p></p><h3>Autocapitalize support on all editable elements and on <form> elements</h3> <p>Improve compatibility with Safari’s implementation of autocapitalize by: - Supporting autocapitalize attribute on any contenteditable element - Allow specifying the autocapitalize attribute on a <form> element to have it apply to all child form fields <a href=https://crbug.com/776618>#</a></p> <p>This feature was specified <a href=https://html.spec.whatwg.org/multipage/interaction.html#autocapitalization>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://docs.google.com/document/d/1pBwWacGm8GsPHCJDbJ3PZ2l1ywz_dACO3sMh5hUmD7E/edit?usp=sharing>https://docs.google.com/document/d/1pBwWacGm8GsPHCJDbJ3PZ2l1ywz_dACO3sMh5hUmD7E/edit?usp=sharing</a></p></p> No linked samples</p><h3>CSS Typed OM (Houdini)</h3> <p>The new CSSOM provides typed style access for developers. This will generally improve performance primarily by removing the need to do lots of string parsing. In addition to this, it will enable performant development of various new Houdini specifications (including custom properties, layout and paint). Only a subset of CSS properties are supported for now: https://chromium.googlesource.com/chromium/src/+/master/third_party/WebKit/Source/core/css/cssom/README.md <a href=https://crbug.com/545318>#</a></p> <p>This feature was specified <a href=https://drafts.css-houdini.org/css-typed-om/>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://developers.google.com/web/updates/2018/03/cssom>https://developers.google.com/web/updates/2018/03/cssom</a><a href=https://docs.google.com/document/d/1a4gFI-iFv5uA3SskHMrt-ZphCJTbNda9U78xlHmektA/view>https://docs.google.com/document/d/1a4gFI-iFv5uA3SskHMrt-ZphCJTbNda9U78xlHmektA/view</a></p></p> No linked samples</p><h3>CSS calc() in media queries</h3> <p>According to the CSS Values 4 spec, math functions such as calc() should be allowed wherever individual CSS values such as numbers are allowed. However, calc() expressions are not currently parsed in media queries. This change would introduce support for parsing calc() expressions inside of media queries. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=421909>#</a></p> <p>This feature was specified <a href=https://drafts.csswg.org/css-values-3/#calc-notation>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://developer.mozilla.org/en-US/docs/Web/CSS/calc>https://developer.mozilla.org/en-US/docs/Web/CSS/calc</a><a href=https://developer.mozilla.org/en-US/docs/Web/CSS/Media_Queries/Using_media_queries>https://developer.mozilla.org/en-US/docs/Web/CSS/Media_Queries/Using_media_queries</a></p></p> No linked samples</p><h3>Do not throw on unimplemented but valid keyframe-specific composite values.</h3> <p>By spec, the following should not throw even if additive/accumulative animations are not yet supported by the browser: // Currently throws on Chrome - should not! element.animate( [ { color: 'red', composite: 'accumulate' }, { color: 'blue', composite: 'add' } ], 2000); ); Firefox does not throw in this case. <a href=http://crbug.com/806139>#</a></p> <p>This feature was specified <a href=https://drafts.csswg.org/web-animations-1/>in this Spec</a>.</p> <h3>ECMAScript ⊃ JSON</h3> <p>A Stage 3 proposal makes ECMAScript a syntactic superset of JSON by allowing line separator (U+2028) and paragraph separator (U+2029) in string literals. <a href=https://bugs.chromium.org/p/v8/issues/detail?id=7418>#</a></p> <p>This feature was specified <a href=https://github.com/tc39/proposal-json-superset>in this Spec</a>.</p> <h3>Feature Policy: control over Device Orientation API</h3> <p>The sensor policy-controlled features are used to control access to a device sensors requested through an event specified in the DeviceOrientation Event Specification. By default, the deviceorientation, deviceorientationabsolute and devicemotion events will be restricted to top-level document and same-origin subframes (it follows from features default allow list 'self'). The default behavior can be modified by explicitly enabling or disabling of the dedicated sensor policy-controlled features. <a href=https://crbug.com/796894>#</a></p> <p>This feature was specified <a href=https://www.w3.org/TR/orientation-event/>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://github.com/WICG/feature-policy/blob/gh-pages/features.md#sensor-features>https://github.com/WICG/feature-policy/blob/gh-pages/features.md#sensor-features</a><a href=https://w3c.github.io/sensors/#feature-policy-api>https://w3c.github.io/sensors/#feature-policy-api</a></p></p> No linked samples</p><h3>Fetch API: AbortSignal and AbortController</h3> <p>A fetch() can be made cancellable by passing an AbortSignal "signal" in the fetch options. Calling abort() on the associated AbortController will then cancel the fetch. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=750599>#</a></p> <p>This feature was specified <a href=https://fetch.spec.whatwg.org/#ref-for-dom-request-signal>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal>https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal</a><a href=https://developer.mozilla.org/en-US/docs/Web/API/AbortController>https://developer.mozilla.org/en-US/docs/Web/API/AbortController</a></p></p> <p>Samples: <a href=https://developers.google.com/web/updates/2017/09/abortable-fetch>https://developers.google.com/web/updates/2017/09/abortable-fetch</a></p></p><h3>Fetch API: keepalive</h3> <p>This option instructs fetch() to perform resource fetching with the keepalive flag set for non-blocking event reporting, analytics, etc. as well as the Beacon API (SendBeacon). <a href=https://crbug.com/695939>#</a></p> <p>This feature was specified <a href=https://fetch.spec.whatwg.org/#ref-for-dom-request-keepalive>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://docs.google.com/document/d/1iHJtFa3jOo5n9QXHb6Ok5nK8kavXSk2DrLoubPWi9ys/edit>https://docs.google.com/document/d/1iHJtFa3jOo5n9QXHb6Ok5nK8kavXSk2DrLoubPWi9ys/edit</a></p></p> No linked samples</p><h3>Function.prototype.toString revision</h3> <p>The "implementation-dependent String" returned from Function.prototype.toString() is now a fully-specified String, which is a substring of the source code that defines the function. For example, this preserves whitespace and comments between the "function" keyword and the function name identifier. For functions created with CreateDynamicFunction (such as through `new Function()`), the String is fully-specified and includes the parameters passed to CreateDynamicFunction. <a href=https://bugs.chromium.org/p/v8/issues/detail?id=4958>#</a></p> <p>This feature was specified <a href=https://tc39.github.io/Function-prototype-toString-revision/>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://github.com/tc39/Function-prototype-toString-revision>https://github.com/tc39/Function-prototype-toString-revision</a><a href=https://tc39.github.io/Function-prototype-toString-revision/>https://tc39.github.io/Function-prototype-toString-revision/</a></p></p> No linked samples</p><h3>Link rel=modulepreload</h3> <p>The new "modulepreload" rel value in <link> element and Link: header provides a way to initiate early (and high-priority) loading of module scripts. <a href=http://crbug.com/740886>#</a></p> <p>This feature was specified <a href=https://html.spec.whatwg.org/multipage/links.html#link-type-modulepreload>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://docs.google.com/document/d/1WebH4IOCswACUbaczx5cGQPVl5mnqcieOd4MRJM2syk/edit?usp=sharing>https://docs.google.com/document/d/1WebH4IOCswACUbaczx5cGQPVl5mnqcieOd4MRJM2syk/edit?usp=sharing</a></p></p> <p>Samples: <a href=https://irori.github.io/modulepreload-demo/>https://irori.github.io/modulepreload-demo/</a></p></p><h3>Make <tr> with transform be a containing block.</h3> <p>Elements with table-row, table-row-group, table-header-group, table-footer-group, table-cell, and table-caption that have a transform property should be containing blocks for fixed position elements. Blink currently does not make <tr>, <tbody>, <tfoot>, and <thead> be a containing block for fixed position elements, which we propose to change. <a href=https://crbug.com/804952>#</a></p> <p>This feature was specified <a href=https://www.w3.org/TR/css-transforms-1/>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://www.w3.org/TR/css-transforms-1/#transformable-element>https://www.w3.org/TR/css-transforms-1/#transformable-element</a><a href=https://www.w3.org/TR/css-transforms-1/#transform-rendering>https://www.w3.org/TR/css-transforms-1/#transform-rendering</a></p></p> <p>Samples: <a href=http://output.jsbin.com/cemigih>http://output.jsbin.com/cemigih</a></p></p><h3>Media Capabilities: decoding</h3> <p>This specification intends to provide APIs to allow websites to make an optimal decision when picking media content for the user. This launch is only about exposing the decoding abilities of the device/system/browser. <a href=https://crbug.com/690364>#</a></p> <p>This feature was specified <a href=https://wicg.github.io/media-capabilities/>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://developers.google.com/web/updates/2017/12/chrome-63-64-media-updates#media-capabilities-decoding-info-api>https://developers.google.com/web/updates/2017/12/chrome-63-64-media-updates#media-capabilities-decoding-info-api</a></p></p> <p>Samples: <a href=https://googlechrome.github.io/samples/media-capabilities/decoding-info.html>https://googlechrome.github.io/samples/media-capabilities/decoding-info.html</a><a href=https://beaufortfrancois.github.io/sandbox/media-capabilities/decoding-info-2.html>https://beaufortfrancois.github.io/sandbox/media-capabilities/decoding-info-2.html</a></p></p><h3>MediaStreamTrack.getCapabilities()</h3> <p>Returns the capabilities of the source associated to a MediaStreamTrack. There is also a variant InputDeviceInfo.getCapabilities(), available in the results of MediaDevices.enumerateDevices(). These devices are used as sources for MediaStreamTrack; in this case, getCapabilities() returns the same values as MediaStreamTrack.getCapabilities(). <a href=http://crbug.com/293292>#</a></p> <p>This feature was specified <a href=https://w3c.github.io/mediacapture-main/#dom-mediastreamtrack-getcapabilities()>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack/getCapabilities>https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack/getCapabilities</a></p></p> No linked samples</p><h3>Network error when blob URL loading fails</h3> <p>Rather than returning a 404 when attempting to read from a invalid/non-existing Blob URL, these fetches should result in a network error. <a href=https://crbug.com/732750>#</a></p> <p>This feature was specified <a href=https://fetch.spec.whatwg.org/#scheme-fetch>in this Spec</a>.</p> <h3>Optional catch binding</h3> <p>This proposal allows the `catch` clause to exist without a parameter. <a href=https://bugs.chromium.org/p/v8/issues/detail?id=6889>#</a></p> <p>This feature was specified <a href=https://tc39.github.io/proposal-optional-catch-binding/>in this Spec</a>.</p> <h4>Resources</h4> No linked docs</p> <p>Samples: <a href=http://2ality.com/2017/08/optional-catch-binding.html>http://2ality.com/2017/08/optional-catch-binding.html</a><a href=https://twitter.com/mathias/status/956209997808939008>https://twitter.com/mathias/status/956209997808939008</a></p></p><h3>RTCRtpSender: dtmf attribute</h3> <p>This attribute allows access to the DTMF feature of a PeerConnection's audio track. It is a replacement for the now non-standard CreateDTMFSender function on a PeerConnection. <a href=https://crbug.com/812587>#</a></p> <p>This feature was specified <a href=http://w3c.github.io/webrtc-pc/#peer-to-peer-dtmf>in this Spec</a>.</p> <h3>Retargeting result of elementFromPoint and elementsFromPoint</h3> <p>Previously elementFromPoint and elementsFromPoint are not per spec, and it may return null incorrectly because it is not retargeting the result correctly. We are fixing it to adhere to the spec by applying the correct retargeting algorithm. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=759947>#</a></p> <p>This feature was specified <a href=https://w3c.github.io/webcomponents/spec/shadow/#extensions-to-the-documentorshadowroot-mixin>in this Spec</a>.</p> <h3>Send “input” Event on activation behavior for radio and file input type</h3> <p>As per spec, on input activation behavior fires a input event, then a change event for radio and file <input > type. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=534245>#</a></p> <p>This feature was specified <a href=https://html.spec.whatwg.org/multipage/input.html#radio-button-state-(type=radio)>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://html.spec.whatwg.org/multipage/input.html#radio-button-state-(type=radio)>https://html.spec.whatwg.org/multipage/input.html#radio-button-state-(type=radio)</a><a href=https://html.spec.whatwg.org/multipage/input.html#file-upload-state-(type=file)>https://html.spec.whatwg.org/multipage/input.html#file-upload-state-(type=file)</a></p></p> No linked samples</p><h3>Send “input” Event on checkbox click</h3> <p>As per spec, click on mutable checkbox fires a click event, then an input event, then a change event. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=534245>#</a></p> <p>This feature was specified <a href=https://html.spec.whatwg.org/#checkbox-state-(type=checkbox)>in this Spec</a>.</p> <h3>Service Worker: Disallow CORS responses for same-origin requests.</h3> <p>With this change, a service worker can no longer respond to a request whose mode is 'same-origin' with a response whose type is 'cors'. This is a security measure added to the Fetch specification via https://github.com/whatwg/fetch/issues/629 and https://github.com/whatwg/fetch/pull/655. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=800234>#</a></p> <p>This feature was specified <a href=https://fetch.spec.whatwg.org/>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://github.com/whatwg/fetch/issues/629>https://github.com/whatwg/fetch/issues/629</a><a href=https://github.com/whatwg/fetch/pull/655>https://github.com/whatwg/fetch/pull/655</a></p></p> No linked samples</p><h3>Service Worker: Non-nullable FetchEvent#clientId</h3> <p>With this change FetchEvent#clientId will return an empty string instead of null when it isn't set, e.g., for a navigation request. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=807818>#</a></p> <p>This feature was specified <a href=https://w3c.github.io/ServiceWorker/#fetchevent>in this Spec</a>.</p> <h3>Service Worker: Requests from embed and object elements skip service workers</h3> <p>Service workers no longer receive fetch events for requests from embed and object elements. This includes both requests for the main resource itself (the src or data attribute) and for any requests from the resulting context (the plugin or HTML context). This change was made to adhere to the specification, which disallows service worker interception due to security considerations. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=771933>#</a></p> <p>This feature was specified <a href=https://w3c.github.io/ServiceWorker/#implementer-concerns>in this Spec</a>.</p> <h3>String.prototype.trimStart / String.prototype.trimEnd</h3> <p>Until now, String.prototype.{trimLeft,trimRight} were non-standard language extensions, required for Web compatibility. The Stage 3 proposal at https://github.com/tc39/proposal-string-left-right-trim standardizes this functionality as String.prototype.{trimStart,trimEnd}, and defines String.prototype.{trimLeft,trimRight} as aliases for backwards compatibility. This patch implements that proposal behind the --harmony-string-trimming flag. <a href=https://bugs.chromium.org/p/v8/issues/detail?id=6530>#</a></p> <p>This feature was specified <a href=https://github.com/tc39/proposal-string-left-right-trim>in this Spec</a>.</p> <h3>The ImageBitmap rendering context for <canvas></h3> <p>A new rendering context that streamlines the display of ImageBitmap objects. This new rendering context uses transfer semantics to take ownership of the pixels of an ImageBitmap object, thus avoiding memory duplication and rasterization overhead. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=658734>#</a></p> <p>This feature was specified <a href=https://html.spec.whatwg.org/multipage/scripting.html#the-imagebitmap-rendering-context>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://developer.mozilla.org/en-US/docs/Web/API/ImageBitmapRenderingContext>https://developer.mozilla.org/en-US/docs/Web/API/ImageBitmapRenderingContext</a></p></p> No linked samples</p><h3>Unprefix CSS Grid Layout gutter properties</h3> <p>Rename gutter properties to remove "grid-" prefix: * grid-gap => gap * grid-row-gap => row-gap * grid-column-gap => column-gap Note that column-gap already exists and is used by css-multicol. The parsing needs to be updated as now the default value is "normal". The old (prefixed) properties names will be kept working as aliases. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=761904>#</a></p> <p>This feature was specified <a href=https://www.w3.org/TR/css-grid-1/#gutters>in this Spec</a>.</p> <h3>WebAudio: AudioParam setter is equivalent to setValueAtTime</h3> <p>When setting the value of an AudioParam via the value setter, the value is updated exactly as if setValueAtTime(newValue, context.currentTime). This includes throwing errors that weren't previously thrown and changing the AudioParam timeline <a href=http://crbug.com/764396>#</a></p> <p>This feature was specified <a href=http://webaudio.github.io/web-audio-api/>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://webaudio.github.io/web-audio-api/#attributes-5>https://webaudio.github.io/web-audio-api/#attributes-5</a></p></p> No linked samples</p><h3>WebAudio: Remove dezippering</h3> <p>Historically, Chrome implemented dezippering such that when the value setter of an AudioParam was used, the value was not changed instantaneously. Instead, an exponential approach equivalent to setTargetValueAtTime was done. The actual time constant used was never specified and depended on the AudioParam. With the spec change in https://github.com/WebAudio/web-audio-api/pull/393, (Sep 2015), all dezippering was removed from the spec. Dezippering will be removed from Chrome. <a href=http://crbug.com/496282>#</a></p> <p>This feature was specified <a href=https://webaudio.github.io/web-audio-api/>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://webaudio.github.io/web-audio-api/#audioparam-transitions>https://webaudio.github.io/web-audio-api/#audioparam-transitions</a><a href=https://github.com/WebAudio/web-audio-api/issues/76#issuecomment-107679878>https://github.com/WebAudio/web-audio-api/issues/76#issuecomment-107679878</a><a href=https://github.com/WebAudio/web-audio-api/pull/393>https://github.com/WebAudio/web-audio-api/pull/393</a></p></p> No linked samples</p><h3>[WebAudio] AudioWorklet</h3> <p>The AudioWorklet allows developers to supply JavaScript to process audio on the audio rendering thread. This processing mechanism ensures the synchronous execution of the author code with other built-in AudioNodes in the audio graph. The AudioWorklet is designed to replace ScriptProcessorNode. ScriptProcessorNode will be deprecated once AudioWorklet is shipped. <a href=https://bugs.chromium.org/p/chromium/issues/detail?id=469639>#</a></p> <p>This feature was specified <a href=https://www.w3.org/TR/webaudio/#audioworklet>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://developers.google.com/web/updates/2017/12/audio-worklet, https://developers.google.com/web/updates/2018/06/audio-worklet-design-pattern>https://developers.google.com/web/updates/2017/12/audio-worklet, https://developers.google.com/web/updates/2018/06/audio-worklet-design-pattern</a></p></p> <p>Samples: <a href=https://googlechromelabs.github.io/web-audio-samples/audio-worklet/>https://googlechromelabs.github.io/web-audio-samples/audio-worklet/</a></p></p><h3>inputmode</h3> <p>The inputmode content attribute is an enumerated attribute that specifies what kind of input mechanism would be most helpful for users entering content into the form control or content editable. <a href=http://crbug.com/244688>#</a></p> <p>This feature was specified <a href=https://html.spec.whatwg.org/multipage/interaction.html#attr-inputmode>in this Spec</a>.</p> <h4>Resources</h4> <p>Docs: <a href=https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/KjKEZ5Ga3k8>https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/KjKEZ5Ga3k8</a></p></p> <p>Samples: <a href=http://output.jsbin.com/teselus/1>http://output.jsbin.com/teselus/1</a></p></p> <h2 id="origin-trial">Origin Trials in-progress in 66</h2> <p>This release of Chrome had 0 new origin trials.</p> <h2 id="flagged">Flagged features in 66</h2> <p>This release of Chrome had 0 are available behind a flag.</p> <h2>Deprecations and Removals</h2> <h3 id="deprecation-policy">Deprecation policy</h2> <p>To keep the platform healthy, we sometimes remove APIs from the Web Platform which have run their course. There can be many reasons why we would remove an API, such as:</p> <ul> <li>They are superseded by newer APIs.</li> <li>They are updated to reflect changes to specifications to bring alignment and consistency with other browsers.</li> <li>They are early experiments that never came to fruition in other browsers and thus can increase the burden of support for web developers.</li> </ul> <p>Some of these changes will have an effect on a very small number of sites. To mitigate issues ahead of time, we try to give developers advanced notice so they can make the required changes to keep their sites running.</p> <p>Chrome currently has a <a href="http://www.chromium.org/blink#TOC-Launch-Process:-Deprecation">process for deprecations and removals of API's</a>, essentially:</p> <ul> <li>Announce on the <a href="https://groups.google.com/a/chromium.org/forum/#!forum/blink-dev">blink-dev</a> mailing list.</li> <li>Set warnings and give time scales in the Chrome DevTools Console when usage is detected on the page.</li> <li>Wait, monitor, and then remove the feature as usage drops.</li> </ul> <p>You can find a list of all deprecated features on chromestatus.com using the <a href="https://www.chromestatus.com/features#deprecated">deprecated filter</a> and removed features by applying the <a href="https://www.chromestatus.com/features#removed">removed filter</a>. We will also try to summarize some of the changes, reasoning, and migration paths in these posts.</p> <h3 id="deprecated">Deprecated features in 66</h3> <p>This release of Chrome had 0 features deprecated.</p> <h3 id="removed">Removed features in 66</h3> <p>This release of Chrome had 0 features removed.</p> </div> </body> </html>