In this case (the forum formatting), I can sympathize with Rosity on having difficulty fixing this, because it's really a browser issue and not a coding/display issue. I was looking at their code and they do not use exact addressing, but percentages which the browser is then responsible for figuring out what that means based on the window size. This should work and collapse for almost all browsers at whatever resolution.

However, what breaks this is not code on Rosity's part, but the browser not being able to handle long URL's (except ones with a ?) because of the lack of spaces (that the browsers use for the line break). If a post has such a long URL without spaces (or any other long text without spaces), it will refuse to make it two lines, thus having to widen the table size. Same thing, of course, is true with images.

Yes, there is a solution that could be implemented, but would people like it is the question if Rosity was to do it. That would involve limiting the image post sizes to 640x480 or something like that, and then having code that does the formatting themselves (usually cutting off the end of the URL and replacing it with ... for display) while still allow the working link. Such code would slow down the system as it would have to analyze every post to see if there was an offending URL line.

Given the audience and the information they have to work with, this is probably the way to handle it. Besides, this is one thing that didn't change in the new layout. It's always done this because the browser has always had this issue.

My 2c