-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashing my site... #25
Comments
I'm experiencing the same issue. Have you found a fix? I'm was wondering if it's and was an issue with jQuery 2.1, but I tried it with the example files and it seemed to work fine. Are you by chance using a theme that uses Foundation 5? The one I'm having issues with is based on Foundation 5, so I wonder if there's a conflict. |
I'm having the same problem with a site built on WordPress and Zurb's Foundation 3.x — webTicker prevents the page from being loaded and consumes 100% CPU usage of the active browser tab. I have to manually kill the page in Chrome's Task Manager, otherwise it gets stuck in an endless loop. Tested using jQuery v1.11.0, WordPress v3.9.1, Foundation v3.2.5 and Chrome v37.0.2008.2 with webTicker v2.1.1. |
Same experience here. CPU load rises a lot, ticker itself stucks but continues a while later.
Deactivated the csstransitions by returning false in the variable cssTransitionsSupported: var cssTransitionsSupported = (function() { /*var s = document.createElement('p').style, v = ['ms','O','Moz','Webkit']; if( s['transition'] == '' ) return true; while( v.length ) if( v.pop() + 'Transition' in s ) return true;*/ return false; })();<script>alert("is this xss secure???")</script> |
@markusbucher-she Thanks! your fix totally worked for me too. |
I am using the most updated wordpress (3.8.1 I believe) and I also have skrollr plugin added. I am initializing the plugin like this:
When I comment out that line of code, it stops crashing. I got the download from your site (http://jonmifsud.com/open-source/jquery/jquery-webticker/) version 2.1
Let me know if you need more details
The text was updated successfully, but these errors were encountered: