I can't seem to find any websites detailing the support for the iframe attribute "allowfullscreen". CanIUse.com doesn't seem to have a listing for it, for example.
Does anyone have the support information for Chrome, Safari, IE and Firefox?
I've started discovering some of my own answers:
FireFox: Added support in v18 (January 8, 2013) - Source
Chrome: Added support in v27 (May 22, 2013) - Source
Safari: Added support in v7 (October 22, 2013) - Source
Internet Explorer: Added support in v11
Microsoft Edge: Supported
It seems to be difficult to find detailed release notes for the other three, unfortunately.
There’s a website dedicated to this attribute: http://www.allowfullscreen.com/. It's not very good, however.
While MSDN has only a rudimental entry, MDN provides a support table in their iframe doc:
FF: 18
Chrome: 17 (webkitallowfullscreen)
IE: no support
Safari: prefix support
Opera: supported
Update:
CanIUse.com reports support in all major browsers now.
Looks like this attribute is part of the HTML 5.1 specification.
This WC3 implementation report claims support in all browsers, so
<iframe allowfullscreen>
should work, except Microsoft browsers which need the -ms- vendor prefix.
Related
When i run HTML5 compatibility test in Android native browser then it see the IndexedDB support marked as "Prefixed", while in Chrome and other it is marked as "Yes".
I understand Chrome latest version has full support for IndexedDB but what does IndexedDB support as "Prefixed" means?
According to Mozilla page:
https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB
"Because the specification is still evolving, current implementations of IndexedDB hide under browser prefixes. Browser vendors may have different implementations of the standard IndexedDB API until the specification has solidified. But once consensus is reached on the standard, the vendors implement it without the prefix tags. Actually some implementations have removed the prefix: Internet Explorer 10, Firefox 16, Chrome 24. When they use a prefix, Gecko-based browsers use the moz prefix, while WebKit-based browsers use the webkit prefix."
As per Josh's comment:
Use something like the following statement to ensure compatibility:
window.indexedDB = window.indexedDB || window.webkitIndexedDB;
The characters 'webkit' are the prefix. You might need to use them in Android, but you no longer need to use them in Chrome (a few years ago you did)
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.
Can someone please elaborate on which versions of Internet Expolorer the HTML5 ★ BOILERPLATE framework supports?
Does it have support for IE versions 7 & 8?
The current version supports IE8+. From https://github.com/h5bp/html5-boilerplate#features:
Cross-browser compatible (Chrome, Firefox, IE8+, Opera, Safari).
Boilderplate v4 supports IE6+, but is no longer maintained:
HTML5 Boilerplate v4 provides legacy browser support (IE 6+, Firefox 3.6+, Safari 4+), but is no longer actively developed.
HTML 5 doesn't work in most versions of IE. So HTML5 boilerplate uses Modenizer and X-UA-Compatible to make most of it work. You can read about all of it on their github profile.
SEE DOCS:
https://github.com/h5bp/html5-boilerplate/blob/v4.2.0/doc/html.md
https://github.com/h5bp/html5-boilerplate/blob/v4.2.0/doc/html.md#modernizr
https://github.com/h5bp/html5-boilerplate/blob/v4.2.0/doc/html.md#x-ua-compatible
I checked on http://caniuse.com/ but can't find anything about compatibility for the vibration API.
Which browsers support it?
Update [2014-03-07]: The Vibration API is now supported by Firefox, Chrome, and Opera. I've also made this information available on on caniuse.com.
Based on this article:
The Vibration API is still primarily unsupported. Firefox 16+ is
currently the only browser with support for the API.
According to Mozilla Developer Network it is supported in Chrome with prefix webkit, in Firefox 11+ with prefix moz and in Firefox 16+ without any prefix.
But as you can check in this Issue in Chromium as of now it is not supperted in Chrome and they seem to be in no hurry as Priority is 2(Normal).
It is not supported in Android strock browser as of now.
Do any browsers support the HTML5 context menu attribute?
This has been added to Firefox 8.
See this for an example of it working https://bug617528.bugzilla.mozilla.org/attachment.cgi?id=554309
Right now, the contextmenu attribute is not supported by any browser version. According to caniuse.com it doesn't have support for any current browser versions (IE 9, Firefox 4, Safari 5, Chrome 11, Opera 11.1, or any mobile browsers - iOS, Opera, or Android). It is unknown if it will be supported in future versions.
It was discussed in April 2010 regarding adding it to Webkit. But it doesn't look like it's been added to the nightlies yet.
According to this wiki page for now there is no any popular layout engine except Firefox's Gecko that fully supports the menu element. Meanwhile, you can try some script solutions, like jQuery Context Menu Plugin.
You can use Modernizr for HTML5 feature detection.
It is working well here with Firefox 9.
Firefox 8 Aurora implements this feature. But unfortunately it doesn't seem to work for me now...
Pretty sure it's supported with a polyfill: https://github.com/medialize/jQuery-contextMenu