This works pretty well in IE9 with no noticeable performance problems on a 5 year old machine. Rather scarily, it also works fine on a Lumia 710 as well! I don't care what anyone says - IE is not a stinking heap of poop.
Just Scroll
81–90 of 109 posts
Re: Just Scroll
#82I might just ditch Firefox because of this webpage. A fresh session of Ffx15 goes up to 1.5 GB memory usage, pushes everything into swap and brings my whole OS to a grinding halt until I kill it. In other words this link is basically a very effective DoS. In Chromium it works fine. Am I the only one having this problem? (Edit: I have several Ffx addons running and no Chromium addons, so the comparison was unfair. May…
With today's Firefox nightly build I see a peak of 337MB with it. Image discarding has improved recently. https://bugzilla.mozilla.org/show_bug.cgi?id=683290
Re: Just Scroll
#83I might just ditch Firefox because of this webpage. A fresh session of Ffx15 goes up to 1.5 GB memory usage, pushes everything into swap and brings my whole OS to a grinding halt until I kill it. In other words this link is basically a very effective DoS. In Chromium it works fine. Am I the only one having this problem? (Edit: I have several Ffx addons running and no Chromium addons, so the comparison was unfair. May…
I had this problem too. Looks like this thing relies on browser implementation details to run properly.
Re: Just Scroll
#84Interesting design concept - but a horrible implementation of it. You can't just go and load a thousand divs and not expect a wide variety of performance issues across all the different platforms. You need to have a tile manager or something behind the scenes the same way that Google maps does, especially when targetting smaller consumer devices with limited hardware specs like tablets and phones. * iOS5 - with an ip…
Re: Just Scroll
#85I might just ditch Firefox because of this webpage. A fresh session of Ffx15 goes up to 1.5 GB memory usage, pushes everything into swap and brings my whole OS to a grinding halt until I kill it. In other words this link is basically a very effective DoS. In Chromium it works fine. Am I the only one having this problem? (Edit: I have several Ffx addons running and no Chromium addons, so the comparison was unfair. May…
Re: Just Scroll
#86I might just ditch Firefox because of this webpage. A fresh session of Ffx15 goes up to 1.5 GB memory usage, pushes everything into swap and brings my whole OS to a grinding halt until I kill it. In other words this link is basically a very effective DoS. In Chromium it works fine. Am I the only one having this problem? (Edit: I have several Ffx addons running and no Chromium addons, so the comparison was unfair. May…
With today's Firefox nightly build I see a peak of 337MB with it. Image discarding has improved recently. https://bugzilla.mozilla.org/show_bug.cgi?id=683290
Re: Just Scroll
#87Wow, this is atrocious on so many levels. 30mb of jpg files? The inner web development nerd in me believes there is a better more efficient way to do this. The length of the page is ridiculously long to scroll and unless you have a Mac with a Magic Mouse and smooth scrolling and not a Windows machine (like I use) the scrolling is super jerky.
Re: Just Scroll
#88Re: Just Scroll
#89Cool to look at? You betcha
Not everything needs to be a technological marvel
Re: Just Scroll
#90Interesting design concept - but a horrible implementation of it. You can't just go and load a thousand divs and not expect a wide variety of performance issues across all the different platforms. You need to have a tile manager or something behind the scenes the same way that Google maps does, especially when targetting smaller consumer devices with limited hardware specs like tablets and phones. * iOS5 - with an ip…
It works very well in IE9 (both desktop and WP7.5). Perhaps you should try it before you slate it.
That would help vastly with things like this, unfortunately it does little for its JavaScript performance, but since this page doesn't seem to execute any JavaScript during scrolling (i think) i guess it's not relevant for this one edge case scenario :-)