Chrome 20

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

Enabled by default in 20

This release of Chrome had 4 new features.

Shows a list of pre-defined options to suggest to the user when entering an input element. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/datalist

Samples: http://simpl.info/datalist

Blob

Allows you to construct Blobs directly (var blob = new Blob(["1234"], {type: 'text/plain'})). Blob() constructor also can take ArrayBufferView directly rather than constructing a blob with ArrayBuffer. #

This feature was specified in this Spec.

Resources

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

No linked samples

Date/time input types

<input type=date>, <input type=datetime>, <input type=datetime-local>, <input type=month>, <input type=time>, and <input type=week>. #

This feature was specified in this Spec.

iframe[srcdoc] attribute

Gives the content of an iframe as a src context to embed (e.g. <iframe seamless srcdoc="<b>Hello World</b>"></iframe>). #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#attr-srcdoc

No linked samples

Origin Trials in-progress in 20

This release of Chrome had 0 new origin trials.

Flagged features in 20

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

iframe[seamless] attribute

The seamless attribute is used to embed and <iframe> in the calling page without scrollbars or borders (e.g. seamlessly) #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#attr-seamless

Samples: http://simpl.info/iframe/

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 20

This release of Chrome had 0 features deprecated.

Removed features in 20

This release of Chrome had 0 features removed.