01-19-2009, 05:48 PM
I was sent to an article on the phpbb.com site that provided information on how to prevent image cut off. I guess there are other forums that see similar problems. After a bunch of people tried different solutions, what seemed the best was to use css to tell the browsers how to handle the image. This css was supposed to work best for different people with different resolutions and browsers. I'm wonder if maybe Safari isn't respecting the css. The code I used is telling the browser to shrink the image to the width of the div for the postbody only if your screen isn't wide enough. So people with wide screens probably don't see any shrinking. People will smaller screens will see some shrinking. The image is supposed to maintain it's aspect ratio so it doesn't look like the circus skinny mirror. I'm including the css code below. If there is something I can do do fix this css to make it work for all browsers, I'll be happy to do that.
The above code is only used for images that are linked to external sites. Below is the css code that I think it used for attaching images to a post (not the gallery). As you can see, attaching images to posts will limit the height, so I assume that would create the scroll bar. Attaching images to a post is like attaching a file to an email. It's different from linking to external sites and different from using the gallery.
The gallery has some special css code that does the "lytebox" effect. That is when you click on an image and it comes to the foreground and grays out the background forum webpage. I'm not sure if there is a problem with that and I'm not sure how many people use that feature. I suspect some people upload stuff to the gallery and then link to it using the "img" button instead of the "albumimg" button. That probably won't work so well, but I think all of this adds to the confusion.
I also wonder if there are too many ways to display images and that could be confusing. But I think that people who use each of these methods really prefer them over other methods, so if one were disabled.. a bunch of people would be upset.
Code:
.postimg {
border-width: 0;
max-width: 100%;
}The above code is only used for images that are linked to external sites. Below is the css code that I think it used for attaching images to a post (not the gallery). As you can see, attaching images to posts will limit the height, so I assume that would create the scroll bar. Attaching images to a post is like attaching a file to an email. It's different from linking to external sites and different from using the gallery.
Code:
.attach-image {
margin: 3px 0;
width: 100%;
max-height: 350px;
overflow: auto;
}The gallery has some special css code that does the "lytebox" effect. That is when you click on an image and it comes to the foreground and grays out the background forum webpage. I'm not sure if there is a problem with that and I'm not sure how many people use that feature. I suspect some people upload stuff to the gallery and then link to it using the "img" button instead of the "albumimg" button. That probably won't work so well, but I think all of this adds to the confusion.
I also wonder if there are too many ways to display images and that could be confusing. But I think that people who use each of these methods really prefer them over other methods, so if one were disabled.. a bunch of people would be upset.