Internet Explorer Unspecified Error Javascript
Contents |
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
Script16389 Unspecified Error Ie 11
about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users script16389: unspecified error. line: 1, column: 1 Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping
Ie11 Script16389 Unspecified Error
each other. Join them; it only takes a minute: Sign up SCRIPT16389: Unspecified error — Javascript code up vote 2 down vote favorite I'm getting a "SCRIPT16389: Unspecified error" for simply defining a small piece of Javascript. This script16389: unspecified error. thing works in all browsers EXCEPT IE (yeah, freaking IE -- don't get me started). I am testing this in IE10, but I was told that this is also happening in IE11. This is all I have in my code where it's failing (!!!): I've looked at other posts that have this same error. None of them script16389 unspecified error jquery answers my question. Ideas, anyone?!? javascript internet-explorer share|improve this question asked Apr 22 '15 at 15:39 Ray K. 5121822 1 put semi-colons after isChild = false and isChild = true –AmmarCSE Apr 22 '15 at 15:42 Works fine in IE11. –Leo Apr 22 '15 at 15:45 window.opener is not supported in IE if the opener is in a different security zone. Check your levels of security in IE and see if the problem occurs again. –Ciprian Apr 22 '15 at 15:46 1 Side note: It's not the problem, but the above can be markedly simplified/shortened: var isChild = window.opener != null; :-) –T.J. Crowder Apr 22 '15 at 15:48 1 @T.J.Crowder, thanks for the new info. I learn new things everyday! :) –AmmarCSE Apr 22 '15 at 15:49 | show 10 more comments 1 Answer 1 active oldest votes up vote 2 down vote accepted I have since discovered that IE spits out this generic error if it doesn't like a piece of Javascript code. I don't remember specifically what the Javascript issue was for this question, but I do remember that once I resolved it, this error went away. EDIT: I seem to keep getting downvotes on this, so let me clarify what I'm talking about. What I'm saying is that a Javascript error -- ANY Javascript error, not something sp
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta
Script16389 Unspecified Error Ie 10
Discuss the workings and policies of this site About Us Learn script16389: unspecified error. angular more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us
Doctype Html Error
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 http://stackoverflow.com/questions/29802481/script16389-unspecified-error-javascript-code you, helping each other. Join them; it only takes a minute: Sign up SCRIPT16389: Unspecified error. jquery.min.js, line 2 character 91826 up vote 11 down vote favorite 1 Another Internet Explorer Javascript error. I can't debug as well since Internet Explorer's debugging tool is even slower than Eclipse which is quite an achievement.... Can anybody see what's http://stackoverflow.com/questions/13912461/script16389-unspecified-error-jquery-min-js-line-2-character-91826 causing the SCRIPT16389: Unspecified error. jquery.min.js, line 2 character 91826 error? jquery internet-explorer share|improve this question edited Jun 25 '15 at 3:04 asked Dec 17 '12 at 10:35 bicycle 5,81443062 1 Errors in jquery.js are usually caused by incorrect usage of a jQuery function. Can you isolate when it happens? What does your page do when it turns up? –Pekka 웃 Dec 17 '12 at 10:38 @Pekka It however only shows in Internet Explorer... When the page is loaded various ajax calls are being made. Like $(document).ready(function() { $.ajax({type: "GET", url: "\/slider.php", }).done(function( html ) { $("#jui").html(html); if ($("#vpo").html().length == 0) activateSlider(); }); –bicycle Dec 17 '12 at 10:40 Strange... the only thing in your code that strikes me as odd is the backslash in the ajax URL, what's it doing there? Other than that, are you 100% sure $("#jui") and $("#vpo") exist? –Pekka 웃 Dec 17 '12 at 10:43 Yes they do. I have to put the backslash because otherwise '/slider.
Sign in Pricing Blog Support Search GitHub This repository Watch 4,414 Star 52,802 https://github.com/angular/angular.js/issues/10367 Fork 26,040 angular/angular.js Code Issues 672 Pull requests 180 Projects 0 Wiki Pulse Graphs New issue "SCRIPT16389: Unspecified error" from AngularJs in IE if no browser history #10367 Closed andrewljones opened this Issue Dec 8, 2014 · 4 comments Projects None yet Labels browser: IE10 component: misc core unspecified error Milestone 1.4.0-beta.6 / 1.... Assignees petebacondarwin 6 participants andrewljones commented Dec 8, 2014 Angular version: 1.3.4 Browser version: Internet Explorer 10 In IE10 (may also occur in other versions of IE as well but haven't got easy access to other versions to test) then if a script16389 unspecified error web application using AngularJs is the very first page loaded in the browser the following JavaScript error may occur: SCRIPT16389: Unspecified error. angular.js, line 4116 character 11 This is coming from the call to factory() in the following: function getService(serviceName) { if (cache.hasOwnProperty(serviceName)) { if (cache[serviceName] === INSTANTIATING) { throw $injectorMinErr('cdep', 'Circular dependency found: {0}', serviceName + ' <- ' + path.join(' <- ')); } return cache[serviceName]; } else { try { path.unshift(serviceName); cache[serviceName] = INSTANTIATING; return cache[serviceName] = factory(serviceName); } catch (err) { if (cache[serviceName] === INSTANTIATING) { delete cache[serviceName]; } throw err; } finally { path.shift(); } } } After further investigation I've found that this appears to be originating from the "cachedState = window.history.state;" statement in the following function. function cacheState() { // This should be the only place in $browser where `history.state` is read. cachedState = window.history.state; cachedState = isUndefined(cachedState) ? nu