User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031002 Build Identifier: 0.5 release download A message with embedded images (that show up in the view message window) is forward or replied to a few times. the final result appears to treat the forwarded section (eg. the bit prefixed with >) as a table, and when printing will not break pages on line breaks, or inbetween the images. - it breaks at the top of the forwarded messages if the whole content of the forwarded bit will not fit on the first page. Reproducible: Always Steps to Reproduce: 1.write message with 2 images embedded 2. forward /reply to yourself a few times 3. try printing at different scales and see where the page breaks end up. Actual Results: puts forwarded section on page 2, first page only contains a few lines of text.. Expected Results: break on lines.. not 'theoretical tables'
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.