Closed Bug 295815 Opened 16 years ago Closed 16 years ago
Floats truncated on page boundary when printing (Print of the second page of Mapquest's driving directions is blank)
131.48 KB, application/pdf
90.81 KB, application/pdf
7.70 KB, text/html
1.83 KB, patch
|Details | Diff | Splinter Review|
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050527 Camino/0.8+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050527 Camino/0.8+ Printing out Mapquest's driving directions results in a blank second page (except the footer and header). This happens in both Camino and Firefox. It prints correctly using Safari. Reproducible: Always Steps to Reproduce: 1. Go to mapquest.com 2. Get directions. 3. Go to the printable page. 4. Print Actual Results: Second page is blank. Expected Results: Second page should contain the remaining maps and text.
Related to bug 274424?
*** Bug 296279 has been marked as a duplicate of this bug. ***
To clairfy, this bug occurs when you get directions with MapQuest and try to print them from the printer-friendly view, not the "normal" view (the problems with that are documented in bug 274424). As the reporter indicated, the first page prints fine, but the second page is blank (except for the header and footer), instead of containing the rest of the directions and maps. If there are supposed to be more than two pages (as in the following testcase), pages after the second don't exist at all in the printout (not even as blank pages). Print Preview does match what actually prints. To reproduce, go to http://tinyurl.com/7z3f7 (a sample set of directions from New York City to Boston), and then use print preview. I plan to attach PDF examples of how it should look (printed from Firefox 1.0.6) and how it ends up looking (printed from the 2005-08-05 Firefox trunk build). Based on my testing, this bug occurs in current trunk builds (2005-08-05) of Firefox and Seamonkey, both on Windows and Mac OS X. This bug does NOT occur on current 1.7-branch builds, such as Firefox 1.0.6, Mozilla 1.7.11, or Camino 0.8.4, so it definitely seems to be a trunk-only problem.
This PDF is a printout of my testcase showing how it prints from Firefox 1.0.6. This is also what the printout looks like printed from Mozilla 1.7.11, Camino 0.8.4, and is similar to how it looks when printed from non-Gecko browsers such as Safari. Note that it is 3 pages long.
This PDF is a printout of my testcase showing how it prints on the 2005-08-05 trunk build of Firefox. This is also how the printout looks on the 2005-08-05 trunk build of Seamonkey. Note that the second page is blank, except for the header and footer, and that there is no third page.
Nominating to block aviary-1.5, as this is a major regression with a top 100 website. Also nominating to block 1.8b4.
As zug_treno said, this is a dupe of bug 274424 *** This bug has been marked as a duplicate of 274424 *** *** This bug has been marked as a duplicate of 274424 ***
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
I'm with Mr. Hessman on this. This is not a dupe of 274424. Mr. Hessman's description DOES match my 296279 (so I'm happy to accept that 296279 is a dupe of 295815). What do the original posters of this bug and 274424 say?
*** Bug 310233 has been marked as a duplicate of this bug. ***
This testcase demonstrates the real problem here. The testcase contains a left-floated div containing lots of text, ending with a line reading "this is the bottom of the FLOAT". This div is then followed by a line reading "this is the bottom of the PAGE". When printing, only the part of the float which fits into the first page is printed, followed, on the second page, by the text outside the float. You can see that the text "this is the bottom of the FLOAT" appears nowhere.
Un-duping, changing summary, and marking "regression". The testcase I attached WFM on Firefox 1.0, for which bug 274424 was filed - so this can not be the same bug.
This regressed between 2005-04-28 and 2005-04-29, probably by bug 240276. CCing ROC and BZ, and requesting blocking 1.8b5, as this regression might affect many pages.
This is fairly simple and low-risk fix. It is possible for the available-space-rect height to be set to UNCONSTRAINED during pagination, when we want to force at least part of the the float to fit. But the mContentArea height will still be constrained so we should only look at that.
16 years ago
16 years ago
Status: NEW → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
Comment on attachment 198016 [details] [diff] [review] fix need approval for this blocker
Attachment #198016 - Flags: approval1.8b5?
Comment on attachment 198016 [details] [diff] [review] fix I'm going to take the liberty of approving this patch for the branch.
Attachment #198016 - Flags: approval1.8b5? → approval1.8b5+
checked into branch.
This appears to be fixed using the 2005-10-01 1.8-branch build on Mac OS X. Great work!
You need to log in before you can comment on or make changes to this bug.