I am always interested in knowing what browsers support what and which are more up to date with CSS, HTML5 and other web technologies. The problem is that most of them only show very old versions like Firefox 4 when Firefox 9 is already out. Chrome 12 when 17 is already in dev channel and other similar examples.
Is there a site or sites that benchmark and test the latest versions of browsers and shows for example, how compatible they are with html5, webgl, css.. and what they support and still not support.
You're looking for http://caniuse.com.
Related
This can be a most common question. But no any clue about browser versions. More over, Angular site itself says as following.
What browsers does Angular work with?
We run our extensive test suite against the following browsers: the latest versions of Chrome, Firefox, Safari, and Safari for iOS, as well as Internet Explorer versions 9-11. See Internet Explorer Compatibility for more details on supporting legacy IE browsers.
If a browser is untested, it doesn't mean it won't work. You can also expect browsers to work that share a large part of their codebase with a browser we test, such as Opera 15 or newer (uses the Blink engine), or the various Firefox derivatives.
— AngularJS FAQ - What browsers does AngularJS work with?
However, there is no any note which versions are supported. I googled, but couldn't find. Any one let me know what browsers and their versions do support which version of angular ?
Browser support of AngularJS:
Internet Explorer: 9+
Versions 1.2 and later of AngularJS do not support Internet Explorer versions 6 or 7.
Versions 1.3 and later of AngularJS dropped support for Internet Explorer 8.
Opera 15+
Firefox, Safari, and Google Chrome
As mentioned in a StackOverflow Question here: Which versions of firefox does angularjs support?, since they say which IE version they support and not Chrome, Safari, or Firefox, it's safe to assume all the versions are working.
Version Support Status
Any version branch not shown in the following table (e.g. 1.6.x) is no longer being developed.
Version Status Comments
1.2.x Long Term Support Last version to provide IE 8 support
1.7.x Long Term Support See Long Term Support section below.
Long Term Support
At this time we will focus exclusively on providing fixes to bugs that satisfy at least one of the following criteria:
A security flaw is detected in the 1.7.x branch of the framework
One of the major browsers releases a version that will cause current production applications using AngularJS 1.7.x to stop working
The jQuery library releases a version that will cause current production applications using AngularJS 1.7.x to stop working.
— AngularJS Documentation - Version Support Status
According to AngularJS document：Internet Explorer Compatibility, the answer should be IE 9。
AngularJS 1.3 has dropped support for IE8. Read more about it on our blog. AngularJS 1.2 will continue to support IE8, but the core team does not plan to spend time addressing issues specific to IE8 or earlier.
The project currently supports and will attempt to fix bugs for IE9 and above. The continuous integration server runs all the tests against IE9, IE10, and IE11.
Please could somebody list the browsers and versions for which the Content-Type: Multipart/X-Mixed-Replace is supported for creating an application based on comet principles. I have read conflicting accounts of its support in Chrome and Internet Explorer - although some reports mention its inclusion in IE 10.
A follow-up question is, how stable is this technology to build real-time applications? I ask because Wikipedia currently lists this Content-Type as experimental.
Thanks in advance!
The page you link to also answers your question. It is supported in FireFox, Chrome and Safari, but not in IE or in Safari on the iPhone. The page doesn't say anything about IE 10, but since it isn't officially released yet, that makes sense.
According to MSDN, though, IE 10 does seem to support Comet streaming.
Apart from IE, it has been around for years (since 1995 actually) and should be very stable. The reason why it is marked experimental, is that it isn't declared an official standard yet.
Apparently Google Analytics already uses this technology and I think they wouldn't if it wasn't stable.
Recently users of my website complained about the lack of support to IE6\7.
Is there an offline tool to test if a page-HTML isn't compatible with a specif browser and where is the problem?
Where can I find a list of things I need to be aware of in order to support IE6?
Update: The problems the users describe are in the UI, <Div>are not in the right places and that kind of problems, not JavaScript issues.
I can't force the users to upgrade theirs browsers.
IE6 is an ancient browser. Tell people who complain about lack of support that it's no longer supported and they should upgrade.
There is no "syntax checking" tool to find all incompatibilities, because the problems are not in syntax but how it's interpreted. There is no way around visual testing I'm afraid.
Here are some interesting SO questions on the topic:
One fix for all IE6 problems
How are programmers tackling ie6 bugs these days?
Running Internet Explorer 6, Internet Explorer 7, and Internet Explorer 8 on the same machine
IE tester is useful for testing across version of internet explorer. It may not tell you what is wrong but you will at least be able to see / verify what users are reporting.
http://www.my-debugbar.com/wiki/IETester/HomePage
I have some offer about this for you :
Try to use Jquery more,because Jquery is compatible with most browsers
there are 3 useful addons for Mozilla : Firebug , Web Developer , IE tab
IE 9 has a developer windows that you can change your page standard into IE 8 or 7
Use syntax liek this :
<link rel="stylesheet" type="text/css" href="Styles/ie-fix.css" />
maybe this is useful dude for you :)
If your users are complaining about IE6, you should give support to IE, thats theory. BUT, if possible do as google has been doing for years, if the user is using IE6/7 or lower show some links to download newer browsers and tell them that their browser is too old.
You can use a seperate stylesheet for IE.
There is a third party software named Utilu. Utilu IE Collection contains multiple standalone versions of the browser Internet Explorer, which can be used at the same time. It has more than 10 versions of IE. But its used for viewing the web pages. This software also has firefox and chrome collections.
HTML5 Application Cache not working in ie8+, so i need some of the solution which makes my resource available even in offline mode in ie8+ browsers, in all other browsers the html5 appcache is working fine, only had problem with ie, so need solution for ie8+.
Try this: Researching HTML5 Offline. They suggest Google Gears, even though it's deprecated (post is from August 2010).
Ie 8 and all 8+ versions does not support html5 offline cache, and even 9 does not support this but recently 10 has a developer document which has this support.
Like the title says I'm just wondering the current support for canvas.toDataUrl? I have it working in Firefox 4 but haven't really tried it in any other browers. When I look it up on Google most of the results are pretty scattered as some are from a year ago. It says its only supported with webkit nightly builds. (which I assume now are the actual releases)
I'd also like to know the support for mobile devices as well.
I personally prefer using caniuse.com for finding out the current browser support. Caniuse covers various major releases of each browser, as well as some mobile browsers. However, I always recommend that with anything mission critical, you test in all browsers just to be on the safe side.
If you take a look again at caniuse.com you will see that the support tables are all color-coded and they tell you whether a browser fully-supports, partially-supports, does not support, or does not support (but a polyfill exists). The canvas.toDataUrl, property would fall under the category of "basic support", which shows that the canvas api (or rather the current working draft for it) is fully supported in all major browsers, and there is a polyfill available for IE.
So while it doesn't go into great detail about the specific properties browsers support, it stands to reason if a browser "fully-supports" the basic canvas API, you can safely assume that includes toDataUrl. Once again, if you dont want to leave things to chance, or if you for some reason do not trust caniuse.com, your best bet is to build a test-suite and personally test your app against all browsers.
Actually it's currently broken in the webkit nightly build, a minor security bug I found a couple days ago:
http://code.google.com/p/chromium/issues/detail?id=91016
But in general in the stable release of Chrome it works just fine. In IE9 it works just fine too.