This mode, toggled via the button above the support table, organizes the support data relative to when each browser version was released. As a result, you can get an idea how support for a feature changed over time.
The tooltip information seen when hovering over versions now also includes the browser's release date, which appears in all three visualization modes.
]]>
While GitHub lacks a direct way of voting issues up or down, a system has been set up where anyone can vote for an issue with a "+1" comment. These votes are then tallied and the resulting list in order of votes is generated here.
]]>
Essentially this was being caused by StatCounter having changed their data sets to handle tablet usage separately, as a result all tablet users weren't being considered in the data.
The bug has now been fixed, and all regional data should be correct. As a result, features may appear to have better support in your country.
]]>
- Pattern attribute for input fields
Recent months have also seen the addition of other features since the last announcement, these include:
- Media Queries: resolution feature
- Crisp edges/pixelated images
- DOM Parsing and Serialization
Many thanks to all GitHub contibutors for your submissions!
]]>
To include the browser to the visible browser columns, you may need to first enable it under Settings.
Note that importing regional data won't yet include any amount for UC Browser, but this should be corrected in a few days once the new regional data is included for September.
]]>
- Font unicode-range subsetting
A number of these were submitted via GitHub, many thanks all the people who helped to contribute!
]]>
Information from IE's and Chrome's official status sites now appears where appropriate in feature table Notes section as well in the Resources section. For the Notes section, an entry is only added when the latest version does not support a given feature.
Additionally, support info for the following three more web technologies was added:
- The dialog element
- CSS background-position edge offsets
- The spellcheck attribute
]]>
By popular demand it is now possible again to see directly what prefixes to use for features that require a prefix. By enabling the Show full prefixes option under Settings, the symbol in each browser version cell is now replaced by the prefix required. Without this option it's still also possible to see the prefix in the cell's tooltip.
Additionally, having been busy with implementing the redesign and work on the beta site for the past while I forgot to take the time to mention what new features were added on the site. Because there's been so many in the past five months, here they are listed by category:
- :placeholder-shown CSS pseudo-class
- Improved kerning pairs & ligatures
- Blending of HTML/SVG elements
- seamless attribute for iframes
- Base64 encoding and decoding
- WOFF 2.0 - A better web font compression format
It's also worth noting that the default feature list now shows the latest added feature first, so if you just click on the "Can I use" text with no other filters used, you'll see the latest feature on top.
]]>
Previously on caniuse there'd be a note on which version this applied to, but in order to better see what browsers have this disabled support, you'll now notice there are flag symbols that appear in the cells for browsers where this applies.
Examples of such features include position: sticky, Scoped CSS and WebVTT.
]]>
So a big thanks for all the feedback on the beta site, one of the changes made is a more contrast-heavy "accessible colors" mode which can be toggled from the Settings panel or directly from this link.
Future site improvements will likely happen directly on caniuse.com, so the beta site currently acts as a mirror.
Thanks again to Lennart Schoors for the new design and everyone else for your feedback!
]]>
Initially it was also my intent to use the beta codebase as the main site before this, but considering the additional improvements made together with the redesign I figure it's best to leave the main site as is for now, give the new design a few weeks of feedback on the beta site, then make the full switch to the new design after that.
So in addition to the new design, changes from the previous beta site include:
- Default order of feature tables is now latest-added first, so you can easily see the latest data added to the site
- Much better mobile experience
- Return of the "Show all" button to quickly see all versions.
- Re-ordered/cleaned up settings
Bugs found can be filed on github.
Once again, a huge shout-out to Lennart at lensco.be and his great design for caniuse!
]]>
- WebVTT - Web Video Text Tracks
- Promises
In the mean I've also been working on the new design for the beta site as well as researching other features. Thanks to everyone involved who's been submitting features and updates!
]]>
Allows user to define the width of the tab character
Allows changes (adding/removing/changing elements or attributes in the DOM) to be detected
- ::selection CSS pseudo-element
Unofficial feature to style user-selected areas
Provide a method of defining the effect resulting from overlaying two layers on a Canvas element.
Offers control over cut, copy and paste events and data
- WebRTC Peer-to-Peer connection
Provides a method to allow users to directly connect to each other, allowing video conferencing when combined with the getUserMedia API.
]]>
IE Mobile 10 has much of the same support as seen in IE10 for desktop, with a few exceptions.
Stay tuned for more and bigger site announcements!
]]>
HTML templates - Method of declaring a portion of reusable markup that is parsed but not rendered until cloned.
JPEG XR - The latest JPEG image format of Joint Photographic Experts Group which boasts better compression and supports lossless compression, alpha channel, and 48-bit deep color over normal jpg format.
Channel messaging - Method for having two-way communication between browsing contexts (using MessageChannel)
Opus audio - Royalty-free open audio codec by Mozilla, which incorporated SILK from Skype and CELT from Xiph.org, to serve higher sound quality and lower latency at the same bitrate.
Pointer Events - This specification integrates various inputs from mice, touchscreens, and pens, making separate implementations no longer necessary and authoring for cross-device pointers easier.
Thanks again to all the wonderful Caniuse GitHub contributors for your additions and updates! In the mean time I've been working heavily behind the scenes on making the site better and more useful to developers, stay tuned for more news on this front.
]]>
- The Shadow DOM allows the creation of widgets that use a DOM separate from the host's document DOM
- The WebP image format that supports both lossy and lossless images at smaller sizes than jpeg or png.
- Intrinsic width & height CSS values like min-content allow more types of layout sized based on content rather than specific measurements.
Thanks again to everyone who helped contribute this data!
]]>
- The non-standard but well-supported user-select: none CSS property makes an element's contents unselectable by the user.
- Scoped styles allow stylesheet rules to be limited by the location of the style element. Currently supported in Firefox 21 and for a longer time in Chrome (but with a flag enabled)
]]>
- Strict Transport Security provides a way to declare that a website is only accessible over a secure connection.
- The CSS outline property provides a way to set a border on an element without affecting its size/layout.
- The new HTML5 download attribute makes it easy to turn any link into a download link, without any additional server-side work.
]]>
- Content Security Policy: A method of defining what resources can be loaded from other domains and which cannot.
- PageVisibility: An API providing events and information relating to the visibility of the page to the user.
- CSS Feature queries (aka @supports): Method to use CSS properties based on the browser's support for certain property/properties.
Also added:
- SVG fragment identifiers: By setting a fragment on an SVG URL, it's possible to specify the part of the SVG image that appears (useful for sprites).
]]>
Now, contributions are possible through pull requests on the feature data at GitHub. This should allow you to either suggest changes to current features or even to include new features altogether. See this document for details if you are interested.
Note that my own updates to the site will of course continue, and the feedback forms (found under each feature table) are still good alternative methods for providing corrections/updates that I may have missed. Let me also take this moment to thank everyone who's done so so far, it's very much appreciated!
So thanks in advance to anyone interested in contributing to the site, I hope this new method will help keep the site of maximum usefulness to the web developer community.
]]>
The CSS3 word-break property allows words to be broken across lines with "break-all" or CJK text to not be broken with "keep-all".
The getComputedStyle DOM method provides a way to retrieve the current styles applied to any given element or element's pseudo-classes.
]]>
Note that the browsers are currently hidden by default (together with Opera Mobile), and can be displayed by either enabling them in the Options panel, clicking the "Show all versions" link on a given table or directly from this link.
The reason for this is that at this point these browsers all have very little market share, and should be of low priority to the average developer that already has many other browsers to test for. But as these are high quality browsers with a lot of feature support, I felt it to be important that the information is available.
In the near future this selection will be stored in localStorage so each time you visit the site the last selected browsers will reappear.
One final note is that since apps tend to be updated regularly and testing older versions of Android apps is near impossible, only the latest version will appear on the site for these browsers.
]]>
The other feature is repeating gradients, which allows CSS gradients to continue in a repeated fashion. Support is largely the same as that of regular CSS gradients.
]]>
This has now changed after adding "Known issues" together with a tab interface for each feature for better organization of notes, issues, resources and the feedback form. Currently not that many features have known issues, so feel free to use a feature table's feedback form if you know of any browser bugs not yet mentioned. Thanks!
]]>
Other recent news include the renaming of the CSS word-wrap property to overflow-wrap, which is currently not supported by any browser (though word-wrap is still allowed by browsers for legacy support).
]]>
Now there is no longer a limit of browser versions to compare, and the table will show all features, starting with those that see the most support in the selected browsers. See this example where current desktop browsers are compared.
Additionally, based on your feedback, the SPDY protocol has now been added as a listed feature on the site.
]]>
Thanks to Zach Leatherman for preliminarily research on the subject!
]]>
Additionally, support levels for two features was changed:
- Support for the box-shadow property is now considered "partial" when support is missing for the "inset" keyword or the blur-radius.
- Support for CSS multi-column is now considered "partial" when support is missing for the break-before, break-after, and break-inside properties.
Finally, there's been some fixes to the site that allow the back and forward buttons to work much more predictably. So thanks for everyone who notified me of the "broken back button" bug!
]]>
- CSS Counters allow you to control numerical values in :before and :after generated content.
- The HTML5 sandbox attribute for iframes provides a more secure way of including content from another domain in an iframe element, by disabling scripts, forms, etc.
]]>
Opera Mobile 12 was released for Android, with a very impressive list of new features including WebGL, getUserMedia and Device Orientation Events.
It also saw the release of the HTML5 Please API, which uses data from the caniuse site. The API allows you to use specify certain web technologies you to use on your site, with a message appearing to browsers users unable to view them.
Finally, by popular demand, four new HTML5 form features have been added as separate tables on the site: Input fields for range (slider), date/time (calendar), colors and numbers.
]]>
The new system shows only versions based on a (customizable) usage share percentage, based on information from StatCounter or from imported data. Current and future versions will always be visible, since that information should be helpful regardless of user share. Additionally, mobile versions will always be shown by default, since their share is currently quite a bit lower from desktop browsers.
To customize the versions shown, click Show options at the top left of the Tables tab, then under Versions shown drag the slider to change the threshold set for versions shown. Setting it farther to the right will increase the percentage of users required for a version to appear. Sliding it all the way to the left will result in all versions being visible. Note that "Total users not shown" will show the total percentage of users being hidden.
The options mentioned above are stored in localStorage, so returning to the site will keep the last used settings.
I hope this change will help developers in targeting only the older versions that matter, while providing the freedom to determine specifically at which point they do or do not.
]]>
- 3D CSS transforms, just like regular transforms, but now in 3D!
- Full Screen API, allows video, canvas, or in fact any other element to be the center of a full screen mode.
For a full list of changes in Firefox 10, see the Firefox 10 for developers page.
]]>
matchMedia allows one to check with JavaScript to see whether CSS Media Queries apply. The new CSS3 font-feature-settings allow authors to enable a large number of various typographical effects found in OpenType fonts. Both features were encouraged by the excellent and informative HTML5 Please site.
Some other minor updates: "Farther future" versions have now been removed for browsers where only (at best) information for the upcoming version is available. Additionally, the Ctrl-F shortcut "hijack" that previously focused the site's search field rather than the browser's in-page search has now been removed. While it was liked by some and intended to be helpful, it was ultimately counter-intuitive and occasionally frustrating to people.
]]>
The Full Screen API allows browsers to enter a full screen mode for videos or any other given element (great for browser-based games). Note that this spec is still heavily in development.
requestAnimationFrame provides a way to improve the smoothness of script-based animation. It also allows the load on browsers to be reduced when animation plays in background tabs.
]]>- Index page as initial page
This should be more helpful than the default feature table list displayed before, as it provides a quick overview of all features included on the site.
- Options now show in a column when opened
- Many minor navigation bugs fixed/CSS prettification
Many thanks go to Dale Sande (@anotheruiguy) for these suggestions!
]]>
- ECMAScript 5 Strict Mode and full ECMAScript 5 compliance
- Inline SVG in HTML5 using the new HTML5 parser
]]>
- CSS Hyphens allow control over when words should be hyphenated at the end of lines. Specifically hypens: auto; will allow hyphenated words without soft hyphens.
- Shared Web Workers allow multiple scripts to communicate with a single Web Worker.
]]>
Statistics are stored locally, so after importing them once the site will automatically load your data on subsequent visits.
The feature is currently still in beta and may see some changes, please let me know if you have any trouble or have suggestions for improvements.
]]>
In other news, as Google+ now allows Pages, users of G+ can now add caniuse to their circles.
]]>
In other news, I've been working on something big for the site these past few weeks...hope to have it out within the next week!
]]>
This allows older, but significant browsers to still appear (like Firefox 3.6) as well as give the option to compare many more browser versions.
]]>
There's a significant number of new features since 2.3, including long-awaited support for SVG.
A number of other features are also new since Android 3.
Note that this information is based only on the emulator and some differences may appear once real devices are tested.
]]>
For the full list, see the comparison table.
This also puts iOS Safari as the site's highest scoring mobile browser.
]]>
- Navigation Timing API, a web performance measuring API and the first one to reach a Working Draft spec.
- Audio API which allows processing and synthesizing audio in the browser.
- CSS Regions, a new CSS3 spec that allows content to flow through multiple elements.
]]>
In other news, Chrome 14 was recently announced, see the wiki for what's new for web developers (and update if you see anything missing!).
]]>
- CSS3 Regions
- CSS3 Hyphenation
- and more!
]]>
Currently the wiki is in very early stages and contains little information. It is my hope that over time this will change and it becomes an easily searchable site for people to find out just what was added when, by browser rather than by feature.
So I invite everyone to sign up and help out in providing information. There's some basic guidelines available, as well as some initial pages set up, which hopefully will be enough for anyone to start adding content. If you have any questions, feel free to ask on talk pages, on twitter or just contact me directly.
Thanks for your help!
]]>
These attributes allow scripts to be loaded when the DOM is ready or when the file is ready, respectively, without holding up the loading of the page.
]]>
Device Orientation provides hooks for events triggered by changing the position, tilt, etc. of a device, while the new strict mode in JavaScript helps you ensure you write more errorless and logical code.
Thanks for the feedback everyone!
]]>
I'd like to try a new, more organized method through Google Moderator. This will allow you to submit your own suggestions as well as vote for those submitted by others. As a result, I should be see which features are most requested and add them in that order.
So please, take a look, and start suggesting and voting for the features you'd love to see included on caniuse.com.
]]>
- The progress element
- Server-sent events (EventSource)
- WebSockets enabled by default again
- The dataset property
- Touch events (for touch screen devices)
Not bad for quick release update!
]]>
Many thanks go to Eric Bidelman for the research done into these features. For those interested in more of the File API, Eric's also just written a book on the HTML5 Filesystem API.
Also with this addition, I'm happy to say the caniuse.com website has now reached over 100 features! Thanks for all your support and suggestions to make this possible.
]]>
Additionally, a number of minor bug fixes were made on the site, most related to navigating from one section to another. Finally, by popular demand, the search box is now focused on page load.
]]>
A related site change is that prefixes now are mentioned where necessary for new DOM/JS API features, where previously they only appeared for CSS properties.
]]>
These pages are customizable, so you can choose which browsers and which "time periods" to display, as well as some of the additional information. To begin setting up a page for embedding, see the Embeddable page generator.
]]>
See the full comparison list for all changes tracked on this site and the Apple site for additional new features.
]]>
When can I use has previously shown up to three previous versions, which is probably enough for most. However, an option has now been added to show all available versions, which appears as a "Show all versions" link in the upper-left corner of each table on the regular site. Another option to show more versions by default may be added in the future.
]]>
Features tracked on caniuse.com include:
- CSS Gradients (linear only)
- File API
Opera Mini 6.1 was also released, but no new rendering engine features were added.
]]>
A significant number of other new features have also been added, but have yet to be added to the site. See the IE10 developer guide for details.
]]>
This version includes support for CSS animations and a number of other improvements.
]]>
Touch events were invented by Apple for the iPhone, and now appear in a W3C specification with support growing in mobile browsers.
TTF/OTF fonts have been around for a while, but until now were missing as a @font-face table on When can I use. With recent (partial) support for IE9, these fonts have pretty good cross-modern-browser support.
]]>
Another new change to WCIU is the addition of tooltips on the table cells, which may be helpful to those having trouble with the color coding.
]]>
You will notice that the Android 3.0 browser shares a spot in the "Current" row with Android 2.3. This is because 2.3 is still the current version for smartphones, while 3.0 is the version for tablets. It is expected that 3.1 will be the version both for phones as well as tablets.
]]>
IndexedDB had been around in the dev channel for quite some time now, so it's nice to see if finally made it in the stable Chrome. The Speech Input API is still in Editor's Draft and does not yet have a WCIU entry (so far Chrome is the first browser to include support).
]]>
The features include:
- CSS Grid Layout (first browser with support!)
Excellent news!
]]>
Additionally, anyone curious about the tests done to gather data for the site can now visit the test suite.
]]>
Additionally, anyone curious about the tests done to gather data for the site can now visit the test suite.
]]>
The browser offers many excellent new features, putting it about at the same level of the iOS Safari.
Note that Opera Mini 6 has also been released, by I have not yet had an opportunity to test it.
One other minor new WCIU feature is that the browser version comparison URLs now use a "+" instead of a "|", which should help the when using the URLs in discussion forums. Older URLs will continue to work, however.
]]>
It should also be noted that Firefox releases are expected to appear much faster now, with version 5 scheduled for June this year.
]]>
Updated CSS Gradients support, which means it now supports the gradients syntax used in the latest the gradients specification (largely like Firefox does).
And support for HTML5 form validation, which allows form fields to require proper values before submitting.
]]>
In other news, the recently added Web Notifications feature has now moved from editor's draft to an official W3C Working Draft.
]]>
The good news here is that data-* attributes can already be used everywhere, but the dataset property is only starting to receive support.
]]>
So until CSS3-UI becomes a Working Draft, the text-overflow feature will be considered "unofficial".
Finally, the "Image Values and Replaced Content" spec is now a Working Draft, so gradients and object-fit are no longer considered "unofficial" features.
]]>
The one new feature added since last Platform Preview is Geolocation, all previous "unknown" features are now "not supported". This puts the default score for IE9 at 62%, the biggest leap any browser version has ever made from the previous one.
It still falls a bit behind other current browsers, being about on par with Firefox 3.6. Notable features missing in IE9 that are supported in all other stable desktop browsers include: CSS3 Border images, CSS3 text-shadow, Web Workers and Offline web apps.
]]>
I recommend the Chrome Experiments website for some nice 3D demos, which should also work if you're running Firefox 4 beta.
]]>
The <details> & <summary> elements offer a way to easily show/hide sections on a webpage. They are not yet natively supported anywhere, but good polyfills are already available allowing them to be used today.
In other news that you are no doubt already aware of, Google Chrome will be dropping support for the H.264 video format in a future build, but not yet one in the scope of the WCIU table.
]]>
The HTML5 <progress> and <meter> elements allow developers to easily display and update progress bars and meter gauges.
]]>
More details on the latest changes in Presto 2.7 can be found here.
NOT included in Opera 11 but still expected in an upcoming version are CSS3 gradients, WOFF fonts and CSS3 multi-columns.
]]>
You may also note that WCIU tables now include parent and child feature links, so it's easier to find related information. For example, the new video format tables are all sub-features of the HTML5 Video element. In the future I intend to include similar data for different audio as well as font types.
]]>
Because of this, I have clarified some version numbers to show the range of versions it refers to, whenever no actual change is made in regards to new features. So we now have Android 2.2-2.3, Opera 9.5-9.6 and Opera 10.0-10.1. This should reduce duplicate information and show which versions match each other.
One other important update is the disabling of Web Sockets by default in Firefox 4 and Opera 11. This is the result of a security issue found in the protocol used. Once a more secure version of the protocol has been released, support will re-enabled by default.
]]>
Another recent change that I forgot to mention was the deprecation of Web SQL Database. It is now a W3C note and not expected to be supported in future browers. The IndexedDB API takes its place.
]]>
Other imminent features like WebGL and MathML support have for now slipped to Chrome 8.
]]>
Another recent announcement was the inclusion of IndexedDB in Chromium, which should be included in Chrome 8.
A correction has also been made to the WOFF feature: previously it said Opera 10.5+ supported this font format, but that is not actually the case.
]]>
In other news, some tweets by an Opera employee have revealed that support for CSS3 multi-columns and the EventSource object will be coming soon to an upcoming version, so for now they're considered supported in Opera 10.70.
]]>
Information on when a prefix is required is now available on When Can I Use, in the form of each prefix appearing in the upper-right corner of the table cell. If no prefix appears, the feature should work fine without it.
Please let me know if any errors were made when I added this information. Thanks!
]]>
In other excellent news, Webkit has recently added support for inline SVG and MathML, so expect to see those soon in an upcoming Chrome build and later in Safari.
]]>
For detailed information on its usage I highly recommend the related HTML5 Doctor article.
]]>
Then there's the new CSS3 Background-image options including background-clip, background-origin and background-size. While nobody's reported this feature as missing, the new properties offer some interesting possibilities and deserve inclusion.
Two other minor updates: I've moved Chrome 6 up to be released later this year, with Chrome 7 in the "future". I've also changed the labels of the "Past" and "Far Past" columns to "Previous version" and "Two versions back" which more accurately describe the browser versions they contain.
]]>
It goes much further than that, however. Other new WCIU features include: Multiple CSS backgrounds, SVG in CSS backgrounds, HTML5 audio, CSS calc(), hsl() and hsla(), and the Canvas Text API. WOFF support is also confirmed (was already expected), and the TTF and OTF font formats also surprisingly appear to be supported now, so @font-face now has proper support instead of partial.
As a result, the default WCIU summary gives IE9 an actual hint of green, beating Safari 3.2 and Opera 10.0. Excellent news, who knows what will come next?
]]>
New WCIU features include Geolocation, WebGL (disabled by default), SVG filters, the Web Open Font Format (.woff) and better SVG SMIL support.
]]>
My sincere apologies for the "spamming" effect this has caused, I do believe the problem has been taken care of now. Please let me know if the problem continues. Thanks!
]]>
Since then, WCIU has mostly become a reference guide to web developers, and the conclusion serves little purpose. I have thus removed it by default, offering the option to enable it using the "Show conclusions" checkbox.
]]>
Other news: since Chrome 6 is now on the dev channel, I expect Chrome 5 to be released soon. Seems like the File API didn't make it to Chrome 5, so it's been bumped to 6.
]]>
Additionally, the Firefox 3.7 nightlies now have HTML5 mode enabled by default, which means it's now considered supported in the Inline SVG in HTML5 feature.
]]>
It's also worth noting that currently no browser supports WebGL by default, it has to be manually enabled.
]]>
The WOFF font format is expected to be supported in IE9 as well as Opera 10.*, since each respective company joined Mozilla in submitting the format to the W3C.
SVG Fonts are no longer expected to appear in Firefox 3.7, despite previous plans. HTML5 form features, however, will have partial support. (thanks again, Magne Andersson)
WebGL support was incorrectly included in Chrome 4 and Opera 10.5, so this has been removed. (thanks to Peter Lubbers)
]]>
In addition to the newly added File API feature, I've also added the Web Sockets API. Still an editor's draft so considered "unofficial", but supported in Chrome 4.
]]>
Having just discovered the official Presto 2.3 web specification page, I've updated Opera 10.*'s CSS3 features. Most I already knew of, but I've now acknowledged support for CSS3 Transitions and Multiple Backgrounds.
Additionally, I noticed the Web Database API is no longer part of Web Storage and have thus adjusted its name and spec URL.
]]>
Chrome 3 is now the "stable" build, and Chrome 4 has been added for the Future. Chrome 3 supports the "audio" element, and Chrome 4 will finally have anti-aliased rounded corners.
Also all features for Firefox 3.6 have now been decided on, so some of the previously mentioned features (SVG-in-CSS, SVG SMIL, etc) have been moved to Firefox 3.7/4.0.
A new "unofficial" feature has also been added to the page: "3D Canvas graphics / WebGL", which has been gaining popularity.
Thanks goes to Magne Andersson for the Firefox info and the reminder to update this feed.
]]>
- Firefox 3.5 final has been released and now appears as "Present".
- Several URLs have been corrected/updated
- Fixes to Chrome support: No client-side DB support, no Web Workers in V2.
]]>