I think this is more opera's problem than the site's, because on the NES videos page, when it gets to a certain point in the loading, the view locks at the top of the page and the scroll bar disappears, and it cannot be scrolled in any other way including but not limited to a find and replace. IMHO it's probably an Opera bug caused by too much data on a page/too long page or something like that, but it would be a brilliant help for me and other Opera users if you split it up into two pages or something.
If this has been discussed before I apologise, at any rate there are tonnes of results when searching Opera so if it hasn't I'd be surprised, I just wanted to bring or re-bring attention to the matter.
I pointed this out long ago to Bisqwit (it happens also on the all-movies list). He basically didn't give a shit because it works in Firefox. Yeah, whatever.
I've suspected it's because the <div> tag exceeds some stupidly high height that overflows on huge pages.And, of course, since the page is built entirely from <div> tags, long pages explode.
This could've been fixed in a billion ways, but in typical fashion nothing was done. i.e., find some other way to fix it... unfortunately, it seems your only choice is to use one of the prerelease builds.
Even moreso because those builds tend to be a bit unstable.
I don't like people like that. Especially since Opera is more standards conforming than Firefox (see the acid 2 test), this is exactly like the IE thing (where people make sites that exploit IE's rendering quirks) but worse, because they think they're writing to standards and that Firefox is the best and all.
The best part is how the NES Movies page is (521,580 + 759,362) bytes, or 1.22MB... and has 227 different things that need to be loaded.
For somebody who constantly whines about "internet terrorism" programs creating hundreds of connections, you'd thing something would be done about this!
I mean, it's not like he'd have to redo the whole code, just splitting it into a certain number of pages would be reasonably simple, wouldn't it? I mean, it's already alphabetically sorted, you could split it into 27 different pages; one for each letter and one for other, that shouldn't be too hard? I mean, I'm no expert, but so many other sites manage it.
*Awaits long speech trying to persuade me that it would be extremly hard to do*
Fun fact: the Wiki engine chokes on itself (note the broken tab code at the bottom)
Even splitting it into pages of 20 movies each, hiding the history, and some other things would've made sense.
I'm sure there'll be some long excuse of why it can't be done, and I'd almost be willing to bet it hinges on how the Movies-xxxxxx page can show a veritable billion different combonations.
I didn't even know it used a wiki engine! Interesting. I must be really unobservant. I assume, although I'm probably incorrect, that it can be done even more easily.
Oh yeah, but if it's on a wiki engine, how come wikipedia doesn't break when I view very long/large pages? If a hack is used, wouldn't it be possible to apply the same hack to this site?
In addition to that, there is a dozen of different wiki engines (TASVideos's is close to TWiki, IIRC), each with different functionality, purposes and syntax.
I would actually like to bring up the point that I'd like to see the NES page broken up a bit. Maybe a A-M and N-Z listing, since the page takes so damm long to load.
Thanks for the kind-spirited feedback.
I'm already looking towards having a chance (time, motivation and energy) of rewriting most of the site from scratch. I've got around 30% of it planned, and I intend to plan the rest along creating it.
Unfortunately at the present moment there's no shortage of distractions, and no ample supply of creative energy either.
Sorry about the problem with Opera, but I really don't know any easy way to fix it. The reason why I cannot relayout the site is that doing so would require undoing entirely what I did that caused that problem to appear, which is reorder the page such that the actual content is sent first and then the menubar. With table layout (i.e. the only layout that I know works on Opera), there's no way to send the right side cell first and then the left side.
Why I want the leftside cell sent last is, because it contains advertisements, and loading those advertisements may stall the rendering for a second or two; it is not nice if the displaying of the actual page content (i.e. the movie listing) is delayed. Hence I want to send the ad cell last, and the contents first.
In regards to table order, you could conceivably move the sidebar to the right of the content. It may not be as popular of a format, but it's not inherently evil or anything.
break it into multiple pages, just like any topic in a forum.
provide the usual dictionnary shortcuts (# et A-Z), and a combobox to select the number of results by page (1, 10, all, etc.).
create a page for a simple bullet list with every link in text format, to help people have a faster access to movies, without having to scroll through kilometers of details on a single page.
I never sleep, 'cause sleep is the cousin of death - NAS
I like your attitude. It's the perfect attitude to encourage admins and developers to make things better because of the positive feelings they get from their hard work.
(long reply citing how long it has been since bug was discovered and reported, loss of hope, etc)
Such are the perils of having a mouse with a back button.
In opera you can just do right click + left click (in that order) to go back.
Yes, but my mouse has one as well (on the side), and it is fairly easily triggered.
The result is that, while multitasking, I attempt to click back and inadvertantly erase my entire post. Whoops.
(For those of you who are going to be smartasses and go "But Firefox doesn't erase the contents of a form when you go back and forth, use it!", the problem is because I try to go back, stop, and manage to somehow break things that I need to reload the page. That is, user error. Opera would probably re-fill the form if I had gone forward, then back. leave my document cache disabled, so the page is reloaded from the server, not my disk, and the contents of the form are returned to defaults... this problem would not exist if I disabled caching.)