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.
Related
I am working on a large web application.
It's been in production now for close to 2 years.
Recently, we have started getting complaints from users regarding some weird display issues.
It seems on certain screens(random as far as I can tell), when Ajax requests being made there is a weird flickering graphic that appears.
Here is a screenshot:
I don't believe this to be a CSS/JS issue.
All of our users use the latest version of chrome
We use Kendo UI and Jquery, but no other frameworks
It happens frequently, but is unrepeatable
It affects multiple users across a number of computers
Has anyone experienced this, or something similar?
This doesn't resolve the actual problem, but fixes the issue. It appears to be an issue with the Chrome setting "User Hardware Acceleration". Shutting this off fixes the problem.
Hopefully a good performance analysis and some refactoring will fix the problem and allow me to turn this feature back on.
I am currently making an angular app for IE8 in conjunction with a version for more modern browsers. I have begun running into some speed problems however. In Firefox/Chrome the initial page loads in roughly a second but in IE8 it can take up to ten or fifteen seconds. I expected IE8 to be slower than modern browsers, but not by this much. I have installed dynatrace to try isolate the problem and as far as I can tell it seems to be the AJAX that is slowing down the site. I am using websockets for the modern browser so it is falling back to long polling, I believe, for IE8. If anybody has had similar experience with this or could point me in the right direction that would be greatly appreciated. Also any general tips on angular optimisation would also be greatly appreciated. If more information is needed just ask and I will share it.
We just got hold of a Samsung Galaxy S4 for testing our mobile website (running latest Touch-Wiz Android 4.2.2 - build JDQ39).
Straight away we noticed some major issues in our site. After some investigation, I discovered that this seems to be due to window.setInterval(fn, repeatInterval) not repeating, and only calling the passed function once.
Please note, there probably isn't a problem with our usage of setInterval, as our code works on all our other devices (lots), the chrome browser on the same device, and on desktop browsers.
I've searched, but can't find any mention of this problem. It seems bizarre to me that such a major bug would not have generated more noise.
My question is: Has anyone else seen this problem? Is it the default browser on 4.2.2, or a Touch-Wiz specific problem? Did you find an elegant work-around?
I've come up with a work-around using self-perpetuating setTimeout(s) but it's a bit nasty, and I'd rather not have to do it like that.
Turns out it wasn't actually setInterval's fault at all. Weirdly enough eval.call(window, 'some js'); seems to stop all intervals from working on this particular browser. Really don't understand how. This is the only phone we've seen it on - it doesn't happen on the stock browser on the S3 (Android 4.2.1).
P.S. The only reason we're doing eval.call is to allow make banner ads which use document.write to add scripts in a one page dynamic loading app. I'd much rather it wasn't there.
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.
I'm developing a web application that uses lots of Javascript and CSS, both of my own creation and through third-party libraries. These include jQuery and Google Maps & Visualization JS APIs.
I've been testing everything in Firefox 3. Things are peachy until it turns out the main target of this webapp is (cue sad trombone) IE7. I'm looking for caveats, advice, libraries, or other references to help make this transition as easy as possible (not that it's actually going to be easy).
I've already tried IE7.js though it hasn't yet shown itself to be the silver bullet I was hoping for. I'm sure that it works as advertised, I think it's just not as all-encompassing as I'd like (example: colors like #4684EE and #DC3912, which are correctly rendered in FF3, are rendered as black in IE7, with or without IE7.js). Are there other libraries out there to help bring IE7 (more) in line with FF3?
A corollary question: what debugger would you recommend for IE7? I'm currently using Firebug Lite, but it runs painfully slowly. Is there anything out there with similar features that I might have missed?
As far as libraries go, jQuery is compatible across all major browsers, so at least you've got that going for you. Without knowing exactly which plugins/modules/libraries you're using, I can't recommend alternatives that are cross-browser compatible.
You could take a look at the Internet Explorer Developer Toolbar. It isn't nearly as good as Firebug, but it's better than nothing.
Get the IETab add-on for Firefox so that you can fire up IE right inside the same tab you test Firefox in. Get the FULL version of Firebug. It will be perfect for you to deal with HTML, CSS, and scripting. HTMLValidator for validating your HTML and CSS. The Web Developer toolbar is a MUST if you don't have it. I can't even go into a fraction of the benefits it has, from images to source viewing to validating scripts it has a lot.
I use a separate stylesheet for IE7. It doesn't have many changes from the original stylesheet, but enough to make viewing in IE7 close to FF. I try not to do ANYTHING for IE6. In fact I encourage the "downfall" of IE6. It's almost ten years old, and full of bugs, and unsupported now!
Unfortunately, Microsoft doesn't really want to be on the same page as the W3C and developers that want web standards so that you don't have deal with what you're going through right now. Regardless of what they SAY, they're still "competing" against the other browsers for control, and it's hurting the developers.
Writing cross browser code is a big topic - you can't really generalize it into "don't float left and padding-left" statements and be done.
Separate stylesheets for ie are messy and not needed IMO.
Generally speaking, firefox fixes broken code in a good bit of cases, so there is a chance that at least some of your stuff looks bad in IE because of open tags that firefox is fixing for you.
Re-slicing a site that's already done might be your easiest way. You should be able to completely redo the CSS from scratch in a few hours tops.
But all this is advice that may not apply - it would be easier to see the code you're talking about.