User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:184.108.40.206) Gecko/20080702 SeaMonkey/1.1.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:220.127.116.11) Gecko/20080702 SeaMonkey/1.1.11 not understood way, but with this update a lot of pages can not be printed anymore example: look that url it seems to be script-related Martin Reproducible: Always Steps to Reproduce: 1. 2. 3.
- Can you print the same pages with some other browser? - Is your printer plugged-in to both the AC mains and the computer? (It may sound silly, but 90% of the time, when I suddenly can't print it's because my printer's USB cable has unplugged itself from the computer.)
Component: General → Printing: Output
Product: SeaMonkey → Core
QA Contact: general → printing
Version: unspecified → 1.8 Branch
hey Tony Thanks for asking, but I know what I do. It looks as the skaling for the printout can be set to "userdefined" and a nonsens-value (like 0 %) by skripts from a page just viewed. Re-scaling from page-preview helps However, this is a multi-problem: neither this (the mis-set scaling-rate) can be seen prior to the printout of blank pages. nor is the rerendering for the print working correctly (printing textline + grafics over page-boardes even when set to fit-to-page) I guess you need to have a look Martin
In reply to comment #3: "Fit to page" means fit to page _width_; if the page is still too long, it will overshoot the bottom of the sheet. You may have to reduce the zoom if that happens.
Just in reply to the comment No.3 Hope you do not mean that. I case the space for the print out is reduced be head/footer-line, the rendering-engine needs to take care of that - and not the user ! It is really nasty if you see the print-preview - select print page one only, and the outcome is two. Martin
do you see this issue still with version 3.6 or 4.0 beta?
Whiteboard: [closeme 2011-03-15]
No response to requested information. Closing as incomplele reports.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.