IE support for stopPropagation() is lacking, and requires workarounds, but I can't tell if the same thing is true for stopImmediatePropagation()- is it safe for all browsers, or does it requires its own set of workarounds?
I was wondering for the browser support of JavaScript's event.stopImmediatePropagation as well, so I decided to test it by checking whether the following method exists:
Event.prototype.stopImmediatePropagation
It's supported on the following desktop browsers:
Internet Explorer 9+
Firefox 10+
Chrome 6+
Safari 5.0+
Opera 15+ (Presto doesn't support stopImmediatePropagation)
The stopPropagation mentioned on the other answer is related to the method natively available on browser for the event object , while the stopPropagation() method of jQuery works fine in all browser (since it's a wrapper for the same task, taking into account the browser capabilities in which this method is run)
Related
I have Old ASP Project that depends on ActiveXObject
and now I want to make my project cross-browser and work on chrome in additional to ie
Can I Find any Plugin that makes chrome support ActiveXObject
Note I tried to use DOMParser() instead of ActiveXObject but it's not working fine
ActiveX is only supported by IE - the other browsers use a plugin architecture called NPAPI. However, there's a cross-browser plugin framework called Firebreath that you might find useful.
Chrome doesn't support ActiveXObject. You could use IE Tab in Chrome.
IE Tab exactly emulates IE by using the IE rendering engine directly within Chrome. This will enable you to use ActiveX controls and test your web pages with different versions of IE.
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.
What are all the browsers that support the window.postMessage call now? I am looking for browsers that support it natively, not through an iFrame hack.
Can I use cross-document messaging
FF3+, IE8+, Chrome, Safari(5?), Opera10+
IE8 does not allow postMessage across windows/tabs
http://blogs.msdn.com/b/ieinternals/archive/2009/09/16/bugs-in-ie8-support-for-html5-postmessage-sessionstorage-and-localstorage.aspx
for more info check here
http://www.openajax.org/member/wiki/Browser_Variation_of_the_Hub_Reference_Implementation_%28Illustrative%29
postMessage is supported in IE8+ HOWEVER
Remember that IE9 and below require data to be passed in string form and not as an object.
IE doesn't like you to call postMessage as soon as page loads (I'm assuming this has to do with the iframe you are posting to needing time to load).
Use a setTimeout to wait one or two seconds before calling postMessage.
It took me hours to figure this out and IE wasn't giving me any error message, it was just silently doing nothing until I added the setTimeout.
If you want to start with a demo which actually does work in IE, check out this nifty tutorial by Ilya Kantor
For what it's worth recently I ran into some odd webkit browser/versions out in the wild that did NOT support postMessage. I was using IE(8) detection as my means for seeking an alternative. Instead, I probably should have just done some something like this:
if(window.postMessage){
console.log('Supports post message');
}
Or likely a bit cleaner:
var pm_is_supported = typeof(window.postMessage) == 'function';
All latest browsers supports that e.g. IE 11, Edge, Firefox 57+, Dafari 11+, iOS Safari 10.2+, Opera mini, Chrome for android, UC Browser etc.
https://caniuse.com/#search=document%20messaging
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.