Note: This was mistakenly included though it did not actually ship.
hrefTranslate attribute on HTMLAnchorElement
The
HTMLAnchorElement now has an hrefTranslate attribute, providing the ability for a page to hint to a user agent's translation engine that the destination site of an href should be translated if followed.
IntersectionObserver Document Root
The
IntersectionObserver() constructor
now takes a Document as the 'root' argument, causing intersections to be calculated against the scrolling viewport of the document. This is primarily targeted towards observers running in an iframe. Previously, there was no way to measure intersection with the scrolling viewport of the iframe's document.
Modernized Form Controls
In version 81, Chrome modernizes the appearance of form controls on Windows, ChromeOS, and Linux while improving their accessibility and touch support. (Mac and Android support are coming soon.) It's hoped that this will reduce the need to build custom form controls. This change is the result of collaboration between Microsoft and Google. For more information, see the
recent talk at CDS or the
MS blog post. For a closer look at the controls,
this page gives an example of all of the elements that changed.
Move onwebkit{animation,transition}XX handlers to GlobalEventHandlers
Until now, the prefixed
onwebkit{animation,transition}XX handlers were only available on the Window object in Chrome. They are
now on HTMLElement and Document as required by the spec. This fix brings Chrome in line with Gecko and Webkit.
Note: This change is intended to improve interoperability on existing web pages. These handlers are still obsolete so web developers should use the non-refixed versions on new pages.
Position State for Media Session
Adds
support for tracking position state in a media session. The position state is a combination of the playback rate, duration, and current playback time. This can then be used by browsers to display position in the UI and with the addition of seeking can support seeking/scrubbing too. For a code sample and demonstration, see
our sample.
SubmitEvent
Chrome now supports
a SubmitEvent type, an
Event subtype which is dispatched on form submission. The
SubmitEvent has a submitter property that refers to attributes of the submitter button including the entry data, the
formaction attribute, the
formenctype attribute, the
formmethod attribute, and the
formtarget attribute.
Currently, applications are doing their own form submission by calling
preventDefault() during
onsubmit. This approach has the limitation that the received event does not include the button that triggered the submission.
WebAudio: ConvolverNode.channelCount and channelCountMode
For a
ConvolverNode, the channelCount
can now be set to 1 or 2. The
channelCountMode can be
"explicit" or
"clamped-max". Previously, a
channelCount of 1 was not allowed and neither was a mode of
"explicit".
This release also extends
ConvolverNode capabilities slightly to allow developers to choose the desired behavior without having to add a
GainNode to do the desired mixing.
WebRTC
RTCPeerConnection.onicecandidateerror event changes
The
candidateerror event
now has an explicit address and port, replacing
hostCandidate.
onclosing Event for RTCDataChannel
Adds the onclosing event to the RTCDataChannel object, which signals to the user of a data channel that the other side has started closing the channel. The user agent will continue reading from the queue (if it contains anything) until the queue is empty, but no more data can be sent.
WorkerOptions for shared workers constructor
Adds the WorkerOptions object as the second argument for a shared worker constructor. The previous second argument, a string containing the worker's name is still supported.
WritableStream.close()
WritableStream objects
now have a close() method that closes a stream if it is unlocked. This is directly equivalent to getting a writer, using the writer to close the stream, and then unlocking it again.
JavaScript
This version of Chrome incorporates version 8.1 of the V8 JavaScript engine. It specifically includes the changes listed below. You can find a complete
list of recent changes in the V8 release notes.
Intl.DisplayNames()
The
Intl.DisplayNames() object lets an app or script
get localized names of language, script, currency codes, and commonly used names of date fields and symbols. This will reduce the size of apps (thereby improving latency), make it easier to build internationalized UI components, reduce translation costs, and provide more consistent translations across the web.
Deprecations, and Removals
This version of Chrome introduces the deprecations and removals listed below. Visit ChromeStatus.com for lists of
current deprecations and
previous removals.
Deprecation and Remove "basic-card" support Payment Handler
This version of Chrome removes the basic-card polyfill for Payment Request API in iOS Chrome. As a result, the Payment Request API is temporarily disabled in iOS Chrome. For full details, see
Rethinking Payment Request for iOS.
Remove supportedType field from BasicCardRequest
Specifying
"supportedTypes":[type] parameter for
"basic-card" payment method shows cards of only the requested type, which is one of
"credit", "debit", or
"prepaid".
The card type parameter has been removed from the spec and is
now removed from Chrome, because of the difficulty of accurate card type determination. Merchants today must check card type with their PSP, because they cannot trust the card type filter in the browser:
- Only issuing banks know the card type with certainty and downloadable card type databases have low accuracy, so it's impossible to know accurately the type of the cards stored locally in the browser.
- The "basic-card" payment method in Chrome no longer shows cards from Google Pay, which may have connections with issuing banks.
Firefox removed
"supportedTypes" in version 65.
Remove the <discard> element
Chrome 81
removes the <discard> element. It is only implemented in Chromium, and is thus not possible to use interoperably. For most use cases it can be replaced with a combination of animation of the 'display' property and a removal (JavaScript) callback/event handler.
Remove TLS 1.0 and TLS 1.1
Note: Removal of TLS 1.0 and TLS 1.1 has been delayed to Chrome 83, which is expected to ship in late May 2020.
This version of Chrome
removes TLS 1.0 and TLS 1.1. TLS (Transport Layer Security) is the protocol which secures HTTPS. It has a long history stretching back to the nearly twenty-year-old TLS 1.0 and its even older predecessor, SSL. Both TLS 1.0 and 1.1 have a number of weaknesses.
- TLS 1.0 and 1.1 use MD5 and SHA-1, both weak hashes, in the transcript hash for the Finished message.
- TLS 1.0 and 1.1 use MD5 and SHA-1 in the server signature. (Note: this is not the signature in the certificate.)
- TLS 1.0 and 1.1 only support RC4 and CBC ciphers. RC4 is broken and has since been removed. TLS's CBC mode construction is flawed and was vulnerable to attacks.
- TLS 1.0's CBC ciphers additionally construct their initialization vectors incorrectly.
- TLS 1.0 is no longer PCI-DSS compliant.
Supporting TLS 1.2 is a prerequisite to avoiding the above problems. The TLS working group has deprecated TLS 1.0 and 1.1. Chrome deprecated these features in version 72 in early 2019.
TLS 1.3 downgrade hardening bypass
TLS 1.3 includes a backwards-compatible hardening measure
to strengthen downgrade protections. However, when we shipped TLS 1.3 last year, we had to partially disable this measure due to incompatibilities with some non-compliant TLS-terminating proxies. Chrome currently implements the hardening measure for certificates which chain up to known roots, but allows a bypass for certificates chaining up to unknown roots. We intend to enable it for all connections.
Downgrade protection mitigates the security impact of the various legacy options we retain for compatibility. This means user's connections are more secure and, when security vulnerabilities are discovered, it is less of a scramble to respond to them. (That, in turn, means fewer broken sites for users down the road.) This also aligns with
RFC 8446.
