Chrome 31

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

Enabled by default in 31

This release of Chrome had 4 new features.

CSS object-fit and object-position

CSS properties that control the position and size of replaced content within the content box #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/CSS/object-fithttps://developer.mozilla.org/en-US/docs/Web/CSS/object-position

No linked samples

DOM3 Wheel Events

Implementation of the standard DOM Level 3 WheelEvent. Currently Blink implements a non standard mousewheel event with a very similar but incompatible API. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/Events/wheel

No linked samples

Device Motion

Provides access to device's physical motion. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/Detecting_device_orientation#Processing_motion_events

No linked samples

devicePixelRatio on zoom

Update window.devicePixelRatio on full page zoom so that it accurately portraitists the ratio between css and device pixels. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/Window/devicePixelRatio

No linked samples

Origin Trials in-progress in 31

This release of Chrome had 0 new origin trials.

Flagged features in 31

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

Canvas focus ring

Adds APIs to the canvas 2D context that make it possible to draw a focus ring around a canvas path and notify the operating system of the bounding box of the focused object for accessibility. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API/Tutorial/Hit_regions_and_accessibility#Focus_rings

No linked samples

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 31

This release of Chrome had 0 features deprecated.

Removed features in 31

This release of Chrome had 0 features removed.