MetaChat is an informal place for MeFites to touch base and post, discuss and
chatter about topics that may not belong on MetaFilter. Questions? Check the FAQ. Please note: This is important.
BTW, I have to say that the "max-width: 550" in the Mecha stylesheet is a royal pain in the ass. It means any image wider than 550 gets resized, and since most browsers do very shitty resizing (nearest neighbor, not even linear let alone bicubic) they look like total ass. To see what I'm talking about, look at the lettering in the "MY POKEMONS" image. Now look at the image directly ( http://i97.photobucket.com/albums/l211/courtsiem/1157061372026.jpg ) without it being on a mecha page. Hey look, no more shitty looking text. Totally annoying as hell, but I understand the point of that is to prevent people from posting huge images that make the page hard to read.
It would also be nice if the post parser didn't disallow height and width attributes to IMG, because if you include those with your IMG it means the browser doesn't have to guess while the page is loading. This means if you follow a link to a deep anchor you actually have a chance of it landing in the right spot instead of somewhere completely unrelated. Of course for this to work people would have to actually use the attributes, but as it is now we can't even do that.
Yes, I don't know why height and width are disallowed... I'll ask seanyboy to see if he can fix that.
As to the resizing, People are sometimes putting huge images in here, and that really turns out looking bad. I do hate the resizing, but I can't really think of anything else to do.
I'd say 640 or even 800 would allow through the majority of the jokey image macros unmolested, but still prevent the "OMG I can't read anything and I have to scroll horizontally" thing when someone posts a 4000x3000 image. Or just state in the rules somewhere "if you post an image that's too big we'll edit it into a link instead of inline".
Okay, I'm having a problem with this... I've removed the min width from img in the css, but the middle column has an absolute position so that it starts just to the right of the left column, and ends just to left of the right column... Which means that if the page resolution is too small to fit in the image, the right column encroaches on it. Like right now, I'm viewing this in 1024 x 768, and in Firefox the middle column isn't long enough to accommodate the large images, so the right column is covering up part of those wide images.
I've tried a couple of fixes to take care of it, but found no love so far.
Ah! I forgot to say that right now I have the right-side column loading last, because I don't want the middle column to wait for the right column to load... if I can figure out how to get the comments page to load the middle column last, we won't have this problem. But I'm confused with the php; the comments are loaded as an include in the main.php, but I don't see what device is keeping the right sidebar from appearing, so I'm having trouble sorting it out...