Chrome Release Summary
+151
Chrome 13
Enabled (4) | Origin Trial (0) | Behind a flag (0) | Deprecated (0) | Removed (0)Enabled by default in 13
This release of Chrome had 4 new features.
File System API (Chromium)
With the FileSystem API, a web app can create, read, navigate, and write to a sandboxed section of the user's local file system.
This feature was specified in this Spec.
Resources
Docs: http://www.html5rocks.com/en/tutorials/file/filesystem/https://developer.mozilla.org/en-US/docs/Web/API/FileSystem
Samples: http://www.htmlfivewow.com/demos/terminal/terminal.html
Navigation Timing API
Allows web applications to access timing information related to navigation and elements.
This feature was specified in this Spec.
Resources
Docs: https://developer.mozilla.org/en-US/docs/Navigation_timing
Samples: http://simpl.info/navigationtiming/
Typed Arrays
Buffers for holding binary data and working with WebGL & Audio API: ArrayBuffer, Float32Array , Int16Array, Uint8Array, etc.)
This feature was specified in this Spec.
Resources
Docs: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Typed_arrays
No linked samplesWeb SQL Database
API exposing an SQLite database
This feature was specified in this Spec.
Origin Trials in-progress in 13
This release of Chrome had 0 new origin trials.
Flagged features in 13
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 13
This release of Chrome had 0 features deprecated.
Removed features in 13
This release of Chrome had 0 features removed.