Chrome Release Summary
+151
Chrome 21
Enabled (4) | Origin Trial (0) | Behind a flag (0) | Deprecated (0) | Removed (0)Enabled by default in 21
This release of Chrome had 4 new features.
CSS Flexbox
A CSS box model optimized for user interface design. In the flex layout model, the children of a flex container can be laid out in any direction, and can "flex" their sizes, either growing to fill unused space or shrinking to avoid overflowing the parent. #
This feature was specified in this Spec.
Resources
Docs: https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Flexible_boxes
No linked samplesDrag and Drop Directories
Allows dragging and dropping entire folders using HTML5 Drag and Drop. Extends the DataTransferItem with a method to get a FileEntry/DirectoryEntry.
This feature was specified in this Spec.
Meta Referrer
Using the referrer metadata attribute, a document can control the behavior of the Referer HTTP header attached to requests that originate from the document.
This feature was specified in this Spec.
getUserMedia
Local component of WebRTC
This feature was specified in this Spec.
Resources
Docs: https://developer.mozilla.org/en-US/docs/Web/API/Navigator/getUserMedia
No linked samplesOrigin Trials in-progress in 21
This release of Chrome had 0 new origin trials.
Flagged features in 21
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 21
This release of Chrome had 0 features deprecated.
Removed features in 21
This release of Chrome had 0 features removed.