649765 - Page 1 of this webpage will not print

Status: RESOLVED INCOMPLETE

(Core :: Printing: Output, defect)

Description

[Nick]

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

Despite displaying on the print preview, page one of the linked page above will not print. Only page 2 prints. Page 1 prints out a blank page.

Reproducible: Always

Steps to Reproduce:
1. navigate to http://itmanagement.earthweb.com/osrc/print.php/3930571
2. print out the article
3. notice how page 1 fails to print

Actual Results:  
only page 2 prints. Page 1 is a blank page only showing the header/footers.

Expected Results:  
I expected page 1 and page 2 to print

Comment 1

[Nick]

Page 1 prints off just fine on Internet Explorer 8 and Chrome.

Comment 2

[Daniel Holbert [:dholbert]]

WORKSFORME on Ubuntu Linux
Mozilla/5.0 (X11; Linux i686; rv:2.2a1pre) Gecko/20110409 Firefox/4.2a1pre

I wonder if this depends on the specific page-splitting location (which varies between Windows & Linux due to print-margin & font-size differences)

Comment 3

[Daniel Holbert [:dholbert]]

(Also WORKSFORME in Firefox 4.0 on Ubuntu)

Comment 4

[aravindm]

Confirmed on Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110413 Firefox/6.0a1

Only Page 2 is printed, Page 1 is printed blank with only headers and footers.
In Firefox 3.6.16 Page 1 is printed and Page 2 is blank.

Comment 5

[Tim (fmdeveloper)]

I get 1 truncated page with Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120313 Firefox/13.0a1 ID:20120313090404

Comment 6

[Daniel Holbert [:dholbert]]

Still WORKSFORME in Ubuntu -- must be OS-specific (probably due to differences in font / margin metrics).

Setting Version to Trunk per comment 5, and confirming based on comment 4 & 5. (sounds like slightly different behavior between those comments, but both with truncation / missing data )

Comment 7

[BugBot [:suhaib / :marco]]

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Comment 8

[Daniel Holbert [:dholbert]]

The affected URL (from comment 0) is 404 now, 12 years later. Hopefully this might've been fixed in the meantime by e.g. bug 1681052 or something else over the years, but no way to know for sure at this point.

--> Closing as incomplete.