Invalid Argument Ie Error
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 40 Star 622 Fork 139 rubenv/angular-gettext interpolatefnwatchaction invalid argument Code Issues 89 Pull requests 22 Projects 0 Pulse Graphs New
Error Invalid Argument. At Anonymous Function
issue Error: Invalid Argument in IE11 #59 Closed IlianIliev opened this Issue May 9, 2014 · ie11 "invalid argument." -angular 19 comments Projects None yet Labels None yet Milestone 1.0.0 Assignees No one assigned 9 participants IlianIliev commented May 9, 2014 When angular invalid argument using interpolation like:
Hello {{ name }}
In IE11 I get the following error: Error: Invalid Argument at interpolateFnWatchAction (http://test.com:8080/bower_components/angular/angular.js:6833:15) at Scope.prototype.$digest (http://test.com:8080/bower_components/angular/angular.js:12332:23) at Scope.prototype.$apply (http://test.com:8080/bower_components/angular/angular.js:12597:13) at Anonymous function (http://test.com:8080/bower_components/angular/angular.js:14104:25) at completeOutstandingRequest (http://test.com:8080/bower_components/angular/angular.js:4297:7) at Anonymous function (http://test.com:8080/bower_components/angular/angular.js:4598:7) undefined The error is shown only If there are variables in the translated text.Angular Ie Error: Invalid Argument
Any ideas what is causing it? slash-84 commented May 23, 2014 Same problem trying to build inside WinJS app nikolay-tzonev commented Jul 4, 2014 I have the same problem in IE 8, 9, 10 and 11. Is there any development on this? I've done some research and it seems the problem is with the nodeValue property of the TextNode object in IE. In the reference here it says "You cannot use expressions to change the nodeValue of a TextNode object.", whatever that means. Meanwhile a possible workaround is to use the filter instead of the directive.
{{ 'Hello ' + name | translate }}
jeffrom referenced this issue Jul 11, 2014 Closed fix invalid argument for interpolations in IE #79 jeffrom commented Jul 11, 2014 This is tested in ie9/win7 and ie10/win8 jeffrom commented Jul 15, 2014 this is now also tested in ie11 <3 nikolay-tzonev commented Jul 17, 2014 Great, it's working now. Thanks! jeSign in Pricing Blog Support Search GitHub This javascript invalid argument exception repository Watch 4,414 Star 52,804 Fork 26,040 angular/angular.js Code interpolatefnwatchaction angularjs -placeholder Issues 672 Pull requests 180 Projects 0 Wiki Pulse Graphs New issue Textarea
Invalid Argument Error In Javascript
placeholder binding causes exception in IE11 #5025 Closed provegard opened this Issue Nov 19, 2013 · 18 comments Projects None yet https://github.com/rubenv/angular-gettext/issues/59 Labels browser: IE10 browser: IE11 frequency: low needs: investigation severity: broken expected use Milestone Backlog Assignees No one assigned 11 participants provegard commented Nov 19, 2013 See the following fiddle: http://jsfiddle.net/provegard/wLBwd/ While the correct placeholder appears, I also get the following stack https://github.com/angular/angular.js/issues/5025 trace in the console: Error: Invalid argument. at interpolateFnWatchAction (http://code.angularjs.org/1.2.1/angular.js:6366:15) at $digest (http://code.angularjs.org/1.2.1/angular.js:11443:21) at $apply (http://code.angularjs.org/1.2.1/angular.js:11682:13) at Anonymous function (http://code.angularjs.org/1.2.1/angular.js:1285:9) at invoke (http://code.angularjs.org/1.2.1/angular.js:3616:18) at doBootstrap (http://code.angularjs.org/1.2.1/angular.js:1283:5) at bootstrap (http://code.angularjs.org/1.2.1/angular.js:1297:5) at angularInit (http://code.angularjs.org/1.2.1/angular.js:1246:5) at Anonymous function (http://code.angularjs.org/1.2.1/angular.js:20126:5) at trigger (http://code.angularjs.org/1.2.1/angular.js:2298:7) IE version is 11.0.9600.16438 jamie-pate commented Dec 3, 2013 Also happens in ie10, attempting to access nodeValue on a parentless TextNode (nodeType=3) // in function addTextInterpolateDirective() node[0].nodeValue = value jamie-pate commented Dec 4, 2013 May be related to #2614 ?? jamie-pate referenced this issue Dec 4, 2013 Closed IE10 fires input event when a placeholder is defined so that form element is in dirty instead of pristine state #2614 aschiebler commented Dec 18, 2013 Here's a temporary workaround... http://stackoverflow.com/a/20649762/1009125 jamie-pate commented Dec 18, 2013 I still prefer capability sniffing over user
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads http://stackoverflow.com/questions/15890561/what-is-the-meaning-of-invalid-argument-and-what-causes-this-error-when-debugg with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up What is the meaning of “Invalid Argument” and what causes this error when debugging JavaScript in Internet Explorer? up vote 1 down vote favorite I am getting the error when using getElementById(). I won't post the entire program since it's invalid argument a homework assignment, but when I comment out this line of code I don't get any more syntax errors. What should I be looking for in the rest of the code that could have caused the problem? document.getElementById("bugOne").style.left = xPos + "px"; Also- what is an "Invalid Argument" error usually caused by? javascript debugging arguments share|improve this question asked Apr 8 '13 at 23:04 user2234760 731214 What version of IE? –gilly3 Apr 8 '13 at 23:10 add a comment| 2 Answers invalid argument ie 2 active oldest votes up vote 4 down vote accepted "Invalid Argument" is going to be a runtime error, not a syntax error. Don't jump to getElementById() as the culprit - you have a lot going on in one line of code. For debugging, it's useful to break up complex statements: var bugOne = document.getElementById("bugOne"); var left = xPos + "px"; bugOne.style.left = left; In IE8, if you set a bad value on a style property, you get an "Invalid argument" error. I'm guessing xPos contains either undefined or NaN. Set a breakpoint in your debugger and examine the value of xPos. share|improve this answer answered Apr 8 '13 at 23:15 gilly3 49k1285126 You're right. xPos is undefined so that must have caused the problem. –user2234760 Apr 8 '13 at 23:17 Although testing in IE8 is good practice - it's still very common in total visitors to your average website. I make a specific habit of not upgrading IE so I'm still stuck in the same past my visitors are (then use Chrome for any non-test browsing). –Chris Moschini Apr 8 '13 at 23:37 @chris - The IE dev tools allow you to view pages in different browser modes. So, you can test IE8 from within IE10. There's really no reason not to upgrade. –gilly3 Apr 9 '13 at 6:29 1 @gilly3 Start up a WinXP VM and compare the same page in real IE8 and the tools. You'll get tool-speci