What is the current support for the slice method?
Currently Chrome 6+, FF 4+:
Firefox 3.6+ (partial file support, but not .slice() yet)
Firefox 4+ (full file support, though I'm unsure which beta this was added in)
Chrome 6+ (full file support)
Of course this list will become outdated, hopefully soon. There's a test available at html5rocks.com for others to test their browser as new releases happen as well.
Related
Google Chrome has #types/chrome for extension developing. Is there same thing for MS Edge? I find some mismatches between chrome and edge browsers and was hoping that types could help a bunch.
You don't need it. Edge is based on Chromium, and the same Chromium extension can be submitted to the Edge extension store.
https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/
If you've already developed an extension for another Chromium-based browser, you can submit it to the Microsoft Edge Add-ons website. You don't need to rewrite your extension, and must verify it works in Microsoft Edge. When you migrate an existing Chromium extension to other Chromium browsers, make sure the same APIs or alternatives are available for your target browser.
For compatibility, make sure the API you use is supported by Edge (Supported APIs for Microsoft Edge extensions)
I'm developing a mobile site using AngularJS (v 1.5) and it doesn't load in Opera mini. So I started searching and found one article about how Opera mini is a proxy based server and it stripes maximum JavaScript data.
But except that one article, I haven't seen it stated explicitly that Opera mini isn't supported, so I'm a bit confused.
I know Angular 2 is supposed to be released with the view of mobile-first architecture, but does Angular 1.x support opera mini?
Thanks in advance.
It seems Opera mini no longer supported by AngularJS. Check this:
https://mobiforge.com/news-comment/angularjs-to-opera-mini-youre-just-not-worth-it
Edited:
Quoting from AngularJS FAQ (latest stable v1.5):
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; for example, older Android (2.3.x) is supported in the sense that we avoid
the dot notation for reserved words as property names, but we don't
actively test changes against it. You can also expect browsers to work
that share a large part of their codebase with a browser we test, such
as Opera > version 12 (uses the Blink engine), or the various Firefox
derivatives.
I am having a difficult time finding information about createMediaElementSource() support. The mozilla MDN shows support starting with version 6.0 but caniuse.com states that safari apparently does not support it.
So what is true? Does safari support this function? If yes, starting from which version?
I ran the MDN test http://mdn.github.io/media-source-buffer/ on all versions of Safari available to me on saucelabs (v6 to v9) and it did not work on any of those versions.
I'm looking for an open source image generation script for Aztec (2D) barcodes:
I can't seem to find any available scripts out there.
There is an Active-X control here that can be used only in IE and an image generator URL here, but these are not useful as it should be a pure javascript solution running under webkit-based browsers that can run in disconnected mode for mobile apps.
Anyone have some old code for this hanging around either written in javascript or that can be ported to javascript?
Thanks.
bwip-js runs in any browser that supports <canvas> – IE 9+, FF 2+, Chrome, Safari 3+, Opera 9+, and Android 2.1+. It also runs server-side in Node. (If you wanted downlevel IE support, try using a <canvas> emulation layer.)
Aztec is among the 83 barcode formats it can draw. Here's a demo of it in action.
Our company develops ERP and CRM, and so far our products support IE and Firefox. Now we want to support Chrome, Safari and even Opera. Is there any comprehensive materials that introduce browser compatibility of JS and CSS? thks!
theres the mozilla dev-center that has a great CSS- and JavaScript-reference. Every entry has information about browser compatibility.
For a quick overview, you cauld also take a look at caniuse.com (CSS and JavaScript) that provides simple tabular lists for the different features.
I've been coding the front-end for over a decade and a half now, and things seem to get better over time in regards to cross-browser compatibility. I've found that if I write and test my code using Firefox, most everything will work flawlessly on Chrome, Opera, Safari and the only thing you'll end up having to debug would be MSIE. 10 years ago I would have told you to code and test using MSIE and debug your code in the end with Netscape.
But yeah, if you follow this, you'll find it easier to make all your scripting and markup fully cross-browser compatible with no bugs at all. Enter IE9, of course, a different monster altogether.
Is there any comprehensive materials that introduce browser
compatibility of JS and CSS?
http://en.wikipedia.org/wiki/Comparison_of_layout_engines_(Cascading_Style_Sheets)
http://html5test.com/
http://caniuse.com/
"Comprehensive" can change overnight, but there is a great deal of information available.
If your products work for the latest version of Firefox, Chrome, Safari, and Opera will work without major flaws most of the time. If your markup is invalid, you are using many vendor-specific extensions, or you are using cutting-edge features, this may not be the case.