I have experienced one great frustration consistently with Firefox: when "many" images are posted in one message, the bottommost ones are not visible.  The postings in this forum apparently push Firefox to some internal limit.

 

For instance, in http://www.urbanohio.com/forum2/index.php?topic=11299.0 the first 58 images in the initial post are displayed. A strip along the top of the 59th is displayed. Then there is a blank space for what appears to be the height of the remaining images down to the end of that post.  When scrolling I can see gray boxes flash by that appear to be in the locations of the invisible images.

 

Images in subsequent reply posts *are* displayed (don't inherit the problem.)

 

It appears (to me) that "too many" image tags within the same <DT> (table cell) are not handled well. This accounts for the following messages' images being displayed. I tracked down the failure using the DOM inspector tool in Firefox and it looks like at some threshold, Firefox just refuses to display further images.

 

Just curious if anyone has found a work around. I saw some old threads on the subject of messed up images but no real fix was suggested (I just upgraded to Firefox 2.0 and that did not help.)

 

TIA.

I have the same problem. 

In Mac 10.4, FF 2.0, the images appear to load but when the page is indicated as being done, absolutely none of the images in the initial post appear.

As you noted the reposts in the replies do appear.

What OS are you using ?

ah yes, the great firefox problem.

 

Though of all of my message boards, it only happens in SMF

I am running Windows XP SP2.

 

Ok - it sounds like the problem is common and there has been no solution found.

 

I had an idea. There is a Firefox extension called Greasemonkey (it is installed into the browser on your PC) that allows you to install scripts that will be run in order to do custom processing of web pages before display. Supposedly you can modify style tags, the HTML itself, or the DOM structure of the document. What I'm gonna do is see if it is possible to create a work around to this problem in Greasemonkey. If so I will post it here.

 

Secondly, I will see if there are any Mozilla developer's groups I can troll with this problem. I would think they would be interested in something an end user can do to break Firefox.