Chrome 33

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

Enabled by default in 33

This release of Chrome had 6 new features.

CSS font-kerning

A CSS property to control text kerning. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/CSS/font-kerning

No linked samples

Opus in MSE and

Ability to play the open source WebRTC preferred audio codec - Opus in MSE and <video> tags on the for the webM and matroska containers. Please note that we have had Opus support in chromium since M25. This change enables Opus playback on MSE and <video> tags. #

This feature was specified in this Spec.

Page Visibility API

Provides an API to ask whether the current tab is visible or not. If you, you might want to throttle back action or set an idle state. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/Guide/User_experience/Using_the_Page_Visibility_API

Samples: http://simpl.info/pagevisibility

VTTCue

The VTTCue interface, part of WebVTT. Previously the members of VTTCue were on the TextTrackCue interface and there was a TextTrackCue constructor, now the VTTCue constructor must be used instead. #

This feature was specified in this Spec.

Web Speech API (synthesis)

Enables web developers to incorporate speech synthesis into their web pages. Uses whatever the platform provides for synthesis. Coming in M71, synthesis will have a few small changes. 1. Exposing the following existing interfaces: SpeechSynthesis, SpeechSynthesisVoice, SpeechSynthesisEvent 2. Adding a constructor to SpeechSynthesisEvent 3. Adding and exposing a new interface, SpeechSynthesisErrorEvent. #

This feature was specified in this Spec.

requestAutocomplete()

Allows a form to be filled out on demand by the browser's autofill. Particularly for mobile applications, this solves the problem of working with long or even multi-page forms. For merchants, this results in improved conversion rates, sorely needed in mobile purchase scenarios. #

This feature was specified in this Spec.

Origin Trials in-progress in 33

This release of Chrome had 0 new origin trials.

Flagged features in 33

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

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 33

This release of Chrome had 0 features deprecated.

Removed features in 33

This release of Chrome had 0 features removed.