OK, figured it out. I had the idea of copying the prefs.js to a clean, previously-working profile (of course, editing the path references inside it) to see if the problem was copied as well. It did, so it was just a problem with the settings.
Then I started looking in about:config for anything that was in a non-default value that *might* be relevant, resetting that value and checking to see if it worked. Eventually I found that, after resetting mailnews.display.disallow_mime_handlers (it was set to 1, I have no idea how that happened...), the problem went away in the clean profile. The description I found of what this setting did also seemed right on the money. "Fine," I thought. "Now I just have to go back to the original profile and reset that." Well... not quite. I did that, and the problem persisted. So I went to look at the *other* settings I had resetted before with no results. A good suspect was mailnews.display.html_as -- and this time it was right on the money! It seems that somehow I had *two* different settings that disabled the display of images in feeds. My guess is that the second of those was inadvertently set in my initial bumbling attempts to fix the first one. So I never got the combination right... Well... problem solved. Thank you for your time. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my smoke signals pit. *Added by TagZilla 0.066.2 running on Seamonkey 2.0.13 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
