jqRangeSlider slow on chrome - javascript

I'm using jqRangeSlider in creating multiple instances on my website.
For some reason, and only on Chrome - it takes a lot of time to render the sliders (about 1.5-2 seconds each X 9). The sliders also move very slowly (again, only chrome).
FF and IE are working perfectly.
I tried removing other JS files, but for no avail. I'm not even sure how to debug such a problem.
Would really appreciate any idea.

OK, I've found the bug.
The issue originated, oddly enough, from a direction:rtl css property on the body element :\
Now works, as usual, faster than FF and IE.
Hope this will help someone.

Related

Scroll-behavior: smooth Not Working in Chrome

I'm in the process of creating a single page site that relies on the scroll-behavior:smooth CSS property and the method .scrollIntoView({behavior:'smooth'}). I use these mainly to provide a smooth transition between sections, not critical but aesthetically pleasing. Suddenly this feature doesn't seem to be working in Google Chrome. I tested out on Firefox and Chrome mobile and in these works.
I made this pen with the basics of my page: https://codepen.io/gabriel-ar/pen/rEjdYb
Temporarily I've been using https://github.com/iamdustan/smoothscroll , and it solves scrollIntoView, but other plugins like PhotoSwipe are not handling transitions well.
Therefore, what is the best fix here? smoothscroll solves part of it, but apparently not everything.
Is this a bug in Chrome?
scroll-behavior:smooth doesn't seem to be the only property affected, what other thing could have stopped working, if any?
Google Chrome Version 106.0.5249.119
I already uninstalled Chrome and reinstalled it. I Also ran a clean install on a sandbox with the same results.
Thank you!
Update & Solution
It seems this is a local issue, just happening on my computer. Thanks for the replies!
I faced the same issue some time ago, and I came up with this solution:
Open new tab
Go to Chrome's Experimental Flags (chrome://flags)
Search for 'smooth scrolling'
Set the flag to enabled
Let me know if that works for you!

Pixi JS fromImage incredible slow on Chrome

I'm using an example from pixi.js, its pretty basic but I have a problem while loading the 'bunny.png'.
This is the example I'm using: http://www.goodboydigital.com/pixijs/examples/1/
On my computer using wamp, the bunny.png takes a whopping 13 seconds and sometimes even more, to load...
It actually works a bit better on Firefox. The load time on firefox is nearly instant, even when refreshing with ctrl+F5.
The online version works on both browsers for me.
Anyone ever had this before?
Ok, the problem was an extension called 'Hola'. For some weird reason that extension ruined my Apache. Removing that extension fixed my problem.

error in Chrome when displaying inline-block li elements

I'm pretty new to web-coding and in my attempt to create jQuery based menu bars complete with dropdowns I have stumbled upon some vast differences between broswers. Below you can see that while FF and Safari are the same, IE is actually behaving and Opera is ok-ish, Chrome gets it totally wrong. As far as I can tell I have all the latest versions.
I removed the code from here and pasted it in: (doesn't want to let me link properly) so: jsfiddle.net/2hCR2/
Just in case, support for older versions of IE (6-7) is not required.
Right now I'm mostly concerned with the positioning aspect. Any assistance is much appreciated!
****EDIT:** After continuing to play with the chrome developer tools I realized that when I manually set the 1st list (pants/t-shirt) to display:block it displays as expected (exactly like FF and Safari in the image) so it appears that this is more of a javascript/jQuery issue not updating the DOM correctly(?). I also noticed that when I put the code is JSFiddle and ran the script in Chrome it produced the same error, but when I ran JSFiddle in FF (exact same fiddle link) it renders correctly.
It does not happen in Chrome Canary (version 24) but it does in stable (version 22). Apparently it is a bug which has been fixed.
You can either wait a month or two so that all Chrome users get the fix, or just use .show() instead of .show(0).

Strange IE bug on hover updated

http://jsfiddle.net/4t6j5/2/ (this seems to be working normally)
http://www.periferi.nu/#filter=.utstallningar (this does not)
Se the jsFiddle where I have tried to reproduce the error using the parts that are erroneous.
So the problem is that in IE8 and down the read more element starts jumping a whole lot instead of simply sliding in from below when the mouse is over the image. Works perfect in most modern browsers but in IE8 and down it starts jumping (especially when hovering the p elements, for some reason).
It appears that when the code from that part is isolated it works.
Why does it behave differently in IE? Any help is appreciated!
Ok after endless hours I have captured the bug in my css file. Strange case but thanks WTK for the direction. Turns out:
html {overflow-y:scroll;}
Was the main problem for some for me unknown reason.
If someone sits on further information as of why this happens in IE please share.
http://jsfiddle.net/4t6j5/3/ (Bug hunting fiddle)

Why is IE8 rendering a page with JavaScript unusable while FF is doing fine?

LINK TO THE PAGE NO LONGER ACTIVE, THANKS FOR VISITING, Rene
Hi,
I have a page here and I can't understand why is IE8 rendering this page so slowly.
Originally I thought it was the scrolling text at the top but it's not as I commented it out with no progress. So then I profiled with developer tools for IE8 and it shows a lot of anonymous functions running which I suspect come from jquery (which is not loaded by me directly) but the developer tools cannot show me the source code for those functions. So I can't pin down the problem on what are those phantom functions running from or why as I have no experience with jquery. I noticed that those functions do not run in FF when I profiled it with FireBug so maybe something is running for IE but not for FF ? I am a bit lost.
Any help/suggestions is greatly appreciated!
Thanks so much,
Rene
I was able to see the process jumping between 79MB and 65MB off and on. It may be an issue of memory not being freed up or perhaps an inefficient background operation that is hanging everything up.
I would go with meder5's advice. I would comment any and all unnecessary code and start with the bare minimum and track performance till you find the bottleneck as you add pieces back in.
Hi I also tested in Chrome 8. Frankly, the page is neither fast in IE nor FF nor Chrome. But its relatively faster in FF and Chrome much than IE. I suppose it has something to do with the different mechanisms of FF/Chrome and IE use handling contents.
By the way, I appreciate that you guys can do very nice animation with javascript&jquery,

Categories