mgagnonlv wrote:Now another problem, alas. Text-only and enriched messages (i.e. text with styles, but not full-HTML pages) display very quickly. However, some full-html messages that look like web pages take a really long time to appear.
..
EDIT. One last note – and that may be the problem – one of the images of that HTML-message doesn't download (broken link)
i looked at this, with some feed messages that had heavy images (30s to load) and your NoGood.txt and GoodOne.txt. they took ~20s and 15s the first time and there was a broken image in NoGood. thereafter GoodOne took 1-2s and NoGood took ~20.
it worked about the same for both Tb w/wo TM. neither display any portion of the message until the load finishes completely. the big difference is that Tb always has a nice progress listener, so you know it's working or not, whereas with TM it's on for half the time and goes away and there is still a significant amount of time in limbo with a blank pane and no feedback (but it does come eventually after the broken image is given up on and the load event is received).
so, nothing to do (on the non core extension level), except having a more accurate progress feedback. note that only the first loads are slow if all images are successful (until a restart clears the cache) and if even 1 image is broken the rendering engine will try the full timeout length on each selection.