Wedge

Public area => Bug reports => The Pub => Archived fixes => Topic started by: agent47 on October 9th, 2012, 03:55 PM

Title: Large images jut out of post area
Post by: agent47 on October 9th, 2012, 03:55 PM

I'm not a regular here at Wedge although I try to be so I don't know if this has already been talked about but I thought I'd mention it anyway. As the screen below shows, large embedded images seem to jut-out of post area.

Tested on: Chrome & Firefox.
Assumption: This may have something to do with the theme Wuthering

(https://dl.dropbox.com/u/915297/jutout.jpg)

Title: Re: Large images jut out of post area
Post by: Arantor on October 9th, 2012, 03:58 PM

Hmm, those are gallery images, not normal images.

Same problem is in SMF, though...

Title: Re: Large images jut out of post area
Post by: agent47 on October 9th, 2012, 04:02 PM

I edited my post. It has something to do with the theme Wuthering. Oh and it's not just gallery images but external images too.

Title: Re: Large images jut out of post area
Post by: Arantor on October 9th, 2012, 04:04 PM

Eh, it's not specifically Wuthering. Weaving does it as well. And it's still the same as in SMF.

(Also, gallery images can't be fixed as easily as regular images - regular images can be fixed by a max posting size, which isn't set here)

Title: Re: Large images jut out of post area
Post by: agent47 on October 9th, 2012, 04:08 PM

Really? I don't seem to have the issue on Weaving.

Title: Re: Large images jut out of post area
Post by: Arantor on October 9th, 2012, 04:17 PM

Well, it's there on Weaving since that's what I'm using ;) But I have to shrink the window a bit for it to be visible.

Title: Re: Large images jut out of post area
Post by: Nao on October 9th, 2012, 04:34 PM

Isn't there a max-width:100% on these thumbs already..?

Title: Re: Large images jut out of post area
Post by: Arantor on October 9th, 2012, 04:57 PM

For regular posted images, the container .bbc_img has a max-width of 650px which doesn't do any good if the container is below that in width (e.g. this page, narrower than 1100px or so, where there's enough room for the sidebar still to be on the side, but not enough to leave the main body of posts with 650px or more.

For gallery images inside posts, img.aext does not supply a max-width at all, neither does its parent a.zoom container tag.

Title: Re: Large images jut out of post area
Post by: Nao on October 9th, 2012, 05:19 PM

The max-width thingy should work..? Can you point me to a sample URL here that shows the problem...?

Title: Re: Large images jut out of post area
Post by: Arantor on October 9th, 2012, 05:27 PM

How about this page? This page, with a browser width of about 1100px and you'll see the problem. Different variation on it, sure, but the same basic problem.

The image is constrained to 650px but that's no use because it's still overflowing out of the container. Were it using max-width: 100%, there wouldn't be a problem - but it's not.

bbc images are fixed to a max width of 650px, regardless of the container's size, Aeva images inserted by media bbc are not constrained at all and display at natural size.

Title: Re: Large images jut out of post area
Post by: Nao on October 9th, 2012, 05:40 PM

Hmm, well... The problem with max-width: 100% in this situation is that you can click the item to view it at max width, like the 'resized' feature usually does. (But this, IIRC, only triggers if you set a hardcoded width on the img tag.)
Maybe an overflow: auto..?

Posted: October 9th, 2012, 05:37 PM

Ouch, that's complicated...
overflow: auto works when applied to a container div (which we can insert automatically.) But it then means that you can't show multiple img tags next to each other...

Something tells me it's going to be a matter of compromise.

Title: Re: Large images jut out of post area
Post by: agent47 on October 13th, 2012, 08:15 PM

I notice that this issue has been sorted out. Someone please mark this topic as solved.
Woopti-doo!

Title: Re: Large images jut out of post area
Post by: Nao on October 13th, 2012, 10:56 PM

Not really solved. Not on par with my usual output...