3 ms·
Loading their demo linked from the word "on" froze my browser for about 20 seconds. Scrolling the page afterward was horrible, very jerky and laggy. I have nos
by ars 14y ago
Loading their demo linked from the word "on" froze my browser for about 20 seconds. Scrolling the page afterward was horrible, very jerky and laggy.
I have noscript installed, but all scripts on that page were allowed.
- brokenparser 14y ago+1, count me unimpressed. Off: A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js:4 On: A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: http://airbnb.github.com/infinity/infinity.js:154 Firefox 14.0.1 without NoScript, Linux 3.4.0.
- gilini 14y agoSame here, but I wouldn't expect much from a jQuery plugin that implements "infinite scroll". Like I need stuff to start loading by itself whenever I reach the bottom of the page. Also, looking at their code, the first thing I laid eyes on was this statement: var infinity = window.infinity = {}; Which, in this context, would be the exact same as var infinity = {};
- brown9-2 14y agoI believe they are doing that to override any functions/objects already bound to window.infinity from other plugins/scripts. Look at the infinity.noConflict() function at the bottom of the source, which seems to be inspired by the jQuery.noConflict().
- gilini 14y agoIt doesn't matter. Both snippets do the exact same thing, except the first has two attributions, the second just one.