What about the delay when loading a humongous table?
I occasionally need to load a page with 10,000 (or more) table cells, and those are always slow, and no one seems to test browser speeds on those.
I occasionally need to load a page with 10,000 (or more) table cells, and those are always slow, and no one seems to test browser speeds on those.
The answer was to provide better tools that allowed users to analyze/interact with the data without having to render 10k rows to the screen.
It's not like they were able to read them all anyway. I'm going to go out on a limb and say unilaterally that anything that's just dumping 10,000 rows to the screen has, a priori, terrible usability.
It's not really a case I feel browser designers ought to spend a lot of time optimizing for.
It started much much much smaller, but they used it so much it grew far beyond it's initial design, and we were never able to come back to it to do something better. (It's an internal tool BTW, so we, i.e. they, just dealt with it.)
Am actually interested, this is not to say it's not actually slow. Just trying to find out why / how slow it is.
I think it was just a totally barebones table, with tr and td of many rows from a table. I also had another one where it made an editable form from the data (the data had a bit more structure than the first, some css, but no onload javascript (just onclick)).
It was handmade, so no hover effects or other things.
Firefox was really slow and my customer eventually switched to using chrome for that page. But it's still slow, just not as slow.
I remember having my browser freeze totally for about 10 minutes (yes I timed it).
The 10 minutes sounds like more of a bug than anything else. I've loaded 20mb heavily-styled "books" in HTML that took ~10 seconds to load, but scrolled like molasses, but I've never seen a large table behave that poorly (though I've only handled 1-2 thousand rows).