Closed Bug 652178 Opened 13 years ago Closed 13 years ago

FIREFOX 4 not printing from ANCESTRY.com correctly

Categories

(Core :: Layout: Floats, defect, P3)

defect

Tracking

()

VERIFIED FIXED
mozilla6

People

(Reporter: Hovermale2000, Assigned: dbaron)

References

Details

(Keywords: regression)

Attachments

(4 files)

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0

Everything was perfect when I was on ANCESTRY.COM . Switched to MOZZILA 4 yesterday & now I cant print 2 or three page documents correctly. Quality is fine but it reverses the pages. Dont know how to explain this but it prints most info on page 2 and whatever is left on page 1. Switched to AOL. I can print fine on AOL but they dont have copy & paste  & memory for repeats on the site.

Reproducible: Always

Steps to Reproduce:
1.go to ANCESTRY.com
2.try to print 2 or more pages
3.prints pages in reverse--Main info on 2nd page whatever is left on 1st page
Actual Results:  
printed pages are not usable

Expected Results:  
normally it prints second page first , which it does but instead of starting where the first page leaves off it starts from bottom of sheet , fills 2nd sheet then prints whats left on 1st sheet
Does the page appear correctly in Print Preview? Can you attach a PDF or scan of the output and attach to this bug?
Component: General → Printing: Output
Product: Firefox → Core
QA Contact: general → printing
Version: unspecified → 2.0 Branch
The first longish page I ran across (~4 pages) prints correctly (or at least, it shows up correctly in print-preview):
http://search.ancestry.com/iexec/?htx=List&dbid=6224
Emery, can you link to a particular page that's printing incorrectly for you?
Sent you two ways to link my site on ANCESTRY.com Have heard no more . Whats the status now.
OK, so I tested with the provided login+password.  What I see happening is that the header with the person's name and birth/death dates prints on page 1.  Then the timeline prints on page 2.

In 3.6, the timeline and "Family Members" over on the right print on page 1 below the header, while "Source information" prints on page 2.

Looking into that.
Component: Printing: Output → Layout: Floats
QA Contact: printing → layout.floats
David, this looks like a float printing issue....

Emery, thank you for the login information!  Now that we have a small testcase for this, we shouldn't need to log in with your credentials anymore.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: 2.0 Branch → Trunk
For some reason the clear is causing us to push the entire outer div to page 2.  My first guess is that we need to unset mIsTopOfPage for clear, but I haven't looked at this code for a while...
Seems like, for some reason, the div with 'clear: both' doesn't get pushed, which makes its parent nscoord_MAX tall, which forces the parent to get pushed.
http://hg.mozilla.org/users/dbaron_mozilla.com/patches/raw-file/a89943274093/push-for-clear fixes this bug, but it causes layout/reftests/printing/381497-f.html to only produce one page rather than two.
Assignee: nobody → dbaron
OS: Windows XP → All
Priority: -- → P3
Hardware: x86 → All
Target Milestone: --- → mozilla6
https://hg.mozilla.org/mozilla-central/rev/ff87496ea7fc
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Hovermale 2000@aol.com--Just tried to print--still the sme results. Will not print 2 page or more correctly
(In reply to comment #16)
> Hovermale 2000@aol.com--Just tried to print--still the sme results

That's expected, assuming you're running Firefox 4. The fix referenced in in comment 15 was checked into on our development trunk (the code that will be released as Firefox 6 in a few months).
Blocks: 652929
Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20100101 Firefox/6.0

Verified issue on Win XP, Windows 7, Mac OS X 10.6 and Ubuntu using the test case from Comment Comment 8.

Setting resolution to VERIFIED FIXED.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.