AngularJS $http.get in IE8 is not working - javascript

I have to develop an angular application in IE8, but I can't reach the server anyway. When I try a $http.get the application is down. The only strange thing is that when I press F12 in the browser (Developer tools) and refresh the web it works perfectly. Does anybody get any answer, please?.

I don't know what version of Angular you're using but as it's said in the doc :
Note: AngularJS 1.3 has dropped support for IE8. Read more about it on our blog. AngularJS 1.2 will continue to support IE8, but the core team does not plan to spend time addressing issues specific to IE8 or earlier.
If not can you show us your code. It's a bit hard to help you without any information.

The problem was the console.log and $log.debug annotations. When I drop them from the code it works perfectly. I suppose IE8 can't read them without the Developer Tools active and it stops working.
Thank you for your answers.

Related

AngularJs very slow on IE

We faced a very huge performance degradation on IE browser while building a large scale web application using AngularJs!
The application works flawlessly smooth on Chrome and FireFox, but very very slow and unacceptable user experience on Internet Explorer 11 !
I've searched many posts and couldn't find a clue on how to identify the problem.
We have rolled back the latest IE patches, but the problem still persists.
Any help would be appreciated. Thanks.
I found it! It was the Angular Material Design library causing all the slowness of the entire page.
Once I removed it, the performance went back as before (very close to Chrome and FireFox).
Thanks #TehAbstraCt for your tip :)
Try dissolving ur app into components, remove a few modules, see with what it works good with what it doesn't, there are many things IE sucks at, for my angularjs app it was the css, start with that.

AngularJS in Internet Explorer 7

Yes, I know, IE 7 is dated and does not support modern technology. **Insert classic Microsoft joke**
However I work for a state University and there is a lot of red tape so for the time being we still partially support IE7 (hopefully that won't be the case soon). Also, I'm really curious about this issue.
I have read through Angular's documentation for supporting old versions of IE and for the most part I can get things to work. But oddly enough, a simple Angular application crashes on IE7 if you populate two attributes with data bound content in the same HTML tag.
For instance if I am looping (ng-repeat) through an object to create a link list, this works just fine:
Google
But this does not work:
Google
In fact it crashes the whole application. Any thoughts?
Here is a working Plunkr http://plnkr.co/edit/znbXJkhiEQXqhTcyYcU4?p=preview just so you can preview some sample code. When I run that code on a static .html page in an IE 7 browser emulator (browserstack.com), nothing shows, not even the "Hello World". Just the Angular templating brackets.
Please let me know if you need more information. Thanks.

Firebug issue: "Step Over" misbehaves with recursive functions

I've had a strange problem in Firebug. Actually, I googled for this and found something on the web.
Issue 5176 on Firebug Project
I don't want to describe the problem as it is exactly the same as described by this link. But... I didn't realise how to fix it. I don't know what does JSD stand for and if I need to update something.
I have up-to-date Debian system, thoung my browser is Iceweasel (Firefox) 17.0.10 and Firebug is 1.11.4
JSD stands for JavaScript Debugger and means the API exposed by Firefox, which is used by Firebug to debug JavaScript within it's Script panel. There's a new version of this API called JSD2, which the Firebug Working Group is adapting for the next major version of Firebug.
Unfortunately there's no way to fix this on the user side, nor will it be fixed in the old JSD API, because Mozilla doesn't maintain it anymore.
Though as soon as the JSD2 is adapted by Firebug this bug will be gone.
Though note, when that version of Firebug is released in the next few months it will require at least Firefox/Iceweasel 29.0 or 30.0. So you'll need to update to the latest version of your browser then.

Tinymce not working in IE from server

I've a Rails application that uses Tinymce to allow users write posts from many forms.
It works perfect in firefox and chrome but it doesn't work in IE. I can assume that but the problem is... it is working perfectly in IE when I try it in my dev enviroment.
When I try to use those forms from server I get these errors:
SCRIPT438: Object doesn't support this property or method 'parentElement',
tiny_mce.js?1364308119 line 1 character 41026
I know this is not too specific but I hope somebody faced this problem before 8-)
Tinymce version is 3.
Thanks in advance

Javascript flipbook application not working in Chrome on Windows 7

Hi. I have a problem with my current site that has me totally stymied.
I have implemented a javascript flipbook (like an ibook) on my website. It works in Firefox, Opera, Mac, on the iPad, etc., but not on Chrome Windows 7. In Chrome Windows 7, when I click, the page turns, and then the application resets back to the original image. In Firefox, however, it works just fine.
I have scoured the code to find the solution, troubleshooted from different angles, but can't solve the problem.
You can view the site in its current condition here : http://www.cambrianvacation.co.uk/powersb
I have only just begun working on this site, and the flipbook just has dummy content, purely for the purpose of getting it to work, so please excuse that.
If anyone can diagnose the problem, I would be very grateful.
P.S. I have only been studying Javascript for a few months, and although I have a basic understanding, it's not enough to resolve this.
It works perfectly fine for me in Windows 7 + Chrome.
Since Chrome is quite aggressive in it's caching policies, you might as well clear Chrome's cache and try again.
I have the same issue, if you go to their website over here: http://flippingbook.com/help/publisher-2/faq/launching-local-publication-in-google-chrome/ they have a guide on how to fix this issue. It is very not handy at all though because it will be fixing the problem for you only not for whoever visits your website.

Categories

Resources