352769 - second page of any yahoo driving directions map will display but will not print

Status: RESOLVED WORKSFORME

(Camino Graveyard :: Printing, defect)

Description

[lcoll9]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051229 Camino/1.0b2
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051229 Camino/1.0b2

This problem occurs both on my PowerBook G4 (10.3.9) and my mom's iMac (10.3). We can see the Yahoo Maps driving directions for any address combo we search, but when we try to print, the second page (with most or all of the directions!) will not print at all, and is completely ignored. What should be a 3-page file (in Safari or other browsers) becomes a 2-page file; the printed pages say page 1 of 2 and page 2 of 2, so it's as if the second page isn't even seen at all by Camino's print function.

Reproducible: Always

Steps to Reproduce:
1.go to maps.yahoo.com/dd
2.type in any two U.S. addresses
3.hit print

Actual Results:  
The directions display correctly on screen, but when printed, the second page of information appears to have vanished. 

Expected Results:  
What is printed should be the same as the information displayed. All info I see on screen should print out, including the driving directions!

Comment 1

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

I'm pretty sure this is a dupe of another bug I triaged at some point, where something about tables is b0rked when printing.

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

It's a table inside a div, but the div doesn't appear to be floated or abs/fixed positioned.

That's not to say it's not bug 154892 and friends (bug 323688, bug 324956, bug 339854, bug 341907), only that making layout testcases makes my head spin :(


Oh, this fixed on the trunk.  It won't be fixed in Camino 1.0.x or Camino 1.1.x, because those releases won't be getting whatever trunk fixes fixed this.

If someone can find the FIXED bug to which this should be duped, please do dupe ;)