Chrome 4

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

Enabled by default in 4

This release of Chrome had 5 new features.

HTTP Strict Transport Security (HSTS)

Header to inform the browser to always request a given domain over SSL, reducing MITM attack surface area. #

This feature was specified in this Spec.

Proprietary CSS reflections

-webkit-box-reflect #

This feature was specified in this Spec.

Proprietary mask properties

-webkit-mask-* (-webkit-mask-clip) #

This feature was specified in this Spec.

WebSocket

The WebSocket JavaScript API provides a simple API for bi-directional communication with web servers. The WebSocket network protocol enables low overhead bi-directional communication with web servers over a persistent TCP connection. #

This feature was specified in this Spec.

Resources

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

No linked samples

X-Frame-Options

The X-Frame-Options HTTP header field protects pages against clickjacking attacks by allowing sites to opt-out of being embedded in cross-origin (or any) contexts. #

This feature was specified in this Spec.

Origin Trials in-progress in 4

This release of Chrome had 0 new origin trials.

Flagged features in 4

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 4

This release of Chrome had 0 features deprecated.

Removed features in 4

This release of Chrome had 0 features removed.