-
Notifications
You must be signed in to change notification settings - Fork 27.5k
IE8: View not rendering | angular.min.js, Line: 84, Column: 219 | SCRIPT445: Object doesn't support this action | apply?function() #5400
Comments
Same problem here, I've been googling for hours, implemented all the recommend solutions. Nothing worked, so I tried the homepage of AngularJS. It turns out that I get the exact same error there... |
Ya you're right I get the same error there as well... |
FYI I tested in versions 1.2.4 and 1.2.5 |
Can you please provide an example that reproduces this issue via plunker or similar? |
angularjs.org was mentioned already, but if we had a plunker or fiddle with tiny app that also suffers from this issue in IE8 it would be faster for us to create a fix. |
Hi, did you test on real IE8? |
I had this issue and fixed it with
Not sure if specific to me or not. |
The line that is referred to is the check whether |
Here is a jsfiddle: http://jsfiddle.net/A59tX/show/ |
Same problem: #5147 |
Here is the updated jsfiddle with my ci build: http://jsfiddle.net/A59tX/2/show/ |
In IE8 the result object of calling `node.querySelectorAll` does not have a `hasOwnPropery` function. However, it should be usable with `forEach`. Related to angular#5400.
In IE8, reading `console.log.apply` throws an error. Catching this errow now. Fixes angular#5400. Fixes angular#5147.
In IE8 the result object of calling `node.querySelectorAll` does not have a `hasOwnPropery` function. However, it should be usable with `forEach`. Related to #5400.
I opened your jsfiddle in IE8 document mode and still get the error... SCRIPT445: Object doesn't support this action |
That's interesting, I have the same problem here in the real IE8. But in IE11 in IE8 document mode your updated jsfiddle works like a charm! |
I should have been more clear... I'm also using IE11 and running the jsfiddle in IE8 document mode and it fails with the same error. |
@petebacondarwin could you double check? I am away until Xmas... |
@tbosch @petebacondarwin Remember that IEs<10 don't have the |
IE11 in IE8 doc mode does not fail for me with @tbosch's updated fiddle. I don't have a real IE8 to test but we do run IE8 in our CI tests so I would expect that this would be flagged there if it failed... If not then someone needs to write a unit test to cause it to happen. |
For me neither, the fiddle is failing in the real IE8... |
I've just checked on the real IE8 in a Windows XP VM and both fiddles work fine. |
the fiddle fails for me in IE11 in IE8 document mode.... go to http://angularjs.org/ and put it in IE8 document mode and it will fail there as well... |
I don't think those "emulated modes" are really supported by angular (since we don't test against them), or MS themselves (http://msdn.microsoft.com/en-us/library/ie/dn384051(v=vs.85).aspx) |
Yeah, IE document modes should die in a fire, what it really creates is O(n^2) different IE versions. I hope they get completely removed in IE12 (IE11 still has Anyway, considering @tbosch made it work in IE11 in IE8 doc mode and native IE8 doesn't experience the bug, I guess it can be merged & closed. EDIT: document modes were deprecated by MS only starting from IE11 (after all these years they learned what most of use had known already for a long time). |
Guess I'll need a VM just to test on IE8 then... Seems the behavior is inconsistent though regardless. @pvdleek That's interesting, I have the same problem here in the real IE8. But in IE11 in IE8 document mode your updated jsfiddle works like a charm! |
Just a note:
Sent from my iPhone On Dec 21, 2013, at 2:00 PM, defa0009 [email protected] wrote: the fiddle fails for me in IE11 in IE8 document mode.... go to http://angularjs.org/ and put it in IE8 document mode and it will — |
Ah, and for testing you need to open the ie dev tools first and then Sent from my iPhone On Dec 21, 2013, at 2:22 PM, defa0009 [email protected] wrote: Guess I'll need a VM just to test on IE8 then... Seems the behavior is inconsistent though regardless. @pvdleek https://github.com/pvdleek That's interesting, I have the same — |
Just to comment on this issue - we have an app in production that supports IE8, and we have not had a problem with this once we implemented |
Hi all, It works fine on all of those configurations! By the way, my first jsfiddle used Angular 1.2.5 which still contained the bug / not my PR. Angular 1.2.6 does already contain the PR. You can double check with this fiddle that is using Angular 1.2.6: http://jsfiddle.net/A59tX/4/show Closing this now. |
In IE8 the result object of calling `node.querySelectorAll` does not have a `hasOwnPropery` function. However, it should be usable with `forEach`. Related to angular#5400.
In IE8, reading `console.log.apply` throws an error. Catching this errow now. Fixes angular#5400. Fixes angular#5147.
In IE8 the result object of calling `node.querySelectorAll` does not have a `hasOwnPropery` function. However, it should be usable with `forEach`. Related to angular#5400.
In IE8, reading `console.log.apply` throws an error. Catching this errow now. Fixes angular#5400. Fixes angular#5147.
Hi, No doubt jsfiddle/Codepen are best site(s) but both have abnormal behavior in IE8. I would recommend people that are still using IE8 to try the new online HTML editor. |
For those who is still facing the issue, try adding the polyfill for console. It worked for me in IE 7 & 8. |
Hi,
I'm under the gun here... we went with AngularJS under the notion it was supported in IE8. When I run the app we are getting
SCRIPT445: Object doesn't support this action
File: angular.min.js, Line: 84, Column: 219
I am using the latest build of AngularJS. I don't think IE8 likes the apply function.
Any help will be greatly appreciated!
return e.apply ? function () {
var a = [];
q(arguments, function (b) {
a.push(d(b));
});
return e.apply(b, a);
} : function (a, b) {
e(a, null == b ? "" : b);
};
The text was updated successfully, but these errors were encountered: