Chrome 146

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

Enabled by default in 146

This release of Chrome had 1 new features.

Sanitizer API

The Sanitizer API offers an easy to use and safe by default HTML Sanitizer API, which developers can use to remove content that may execute script from arbitrary, user-supplied HTML content. The goal is to make it easier to build XSS-free web applications. This follows previous attempts at establishing a Sanitizer API (https://chromestatus.com/feature/5786893650231296), which we unshipped again (https://chromestatus.com/feature/5115076981293056). The specification has meanwhile progressed and now has widespread support. #

This feature was specified in this Spec.

Resources

No linked docs

Samples: https://developer.mozilla.org/en-US/docs/Web/API/HTML_Sanitizer_APIhttps://sanitizer-api.dev

Origin Trials in-progress in 146

This release of Chrome had 0 new origin trials.

Flagged features in 146

This release of Chrome had 2 are available behind a flag.

Permissions Policy: focus-without-user-activation

A permissions policy to restrict the use of programmatic focus, when not triggered by a user activation. The proposed policy provides a way to control access to the focus API without user activation. The immediate use case would be restricting all sandboxed frames. Focus API, in this context refers to focus management API and autofocus. #

This feature was specified in this Spec.

Playback Statistics API for WebAudio

This feature adds an AudioContext.playbackStats attribute which returns an AudioPlaybackStats object. This object provides audio playback statistics such as average latency, minimum/maximum latency, underrun duration, and underrun count. This API allows web applications to monitor audio playout quality and detect glitches. Note: This feature was previously tracked as AudioContext.playoutStats. It has been renamed to AudioContext.playbackStats to align with the final Web Audio API specification. The old name is supported as a deprecated alias for backward compatibility. #

This feature was specified in this Spec.

Deprecations and Removals

Deprecation policy

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:

• They are superseded by newer APIs.
• They are updated to reflect changes to specifications to bring alignment and consistency with other browsers.
• They are early experiments that never came to fruition in other browsers and thus can increase the burden of support for web developers.

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.

Chrome currently has a process for deprecations and removals of API's, essentially:

• Announce on the blink-dev mailing list.
• Set warnings and give time scales in the Chrome DevTools Console when usage is detected on the page.
• Wait, monitor, and then remove the feature as usage drops.

You can find a list of all deprecated features on chromestatus.com using the deprecated filter and removed features by applying the removed filter. We will also try to summarize some of the changes, reasoning, and migration paths in these posts.

Deprecated features in 146

This release of Chrome had 0 features deprecated.

Removed features in 146

This release of Chrome had 0 features removed.