Closed
Bug 421890
Opened 16 years ago
Closed 16 years ago
"Print Selection" prints blank pages
Categories
(Core :: Printing: Output, defect, P2)
Core
Printing: Output
Tracking
()
RESOLVED
DUPLICATE
of bug 402264
People
(Reporter: Gabri, Assigned: dholbert)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008031004 Minefield/3.0b5pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008031004 Minefield/3.0b5pre If I need to print only a selection of words, Firefox 3 don't print anything. Reproducible: Always Steps to Reproduce: 1.Click on File-Print... (CTRL+P) 2.Click on "Selection" radio button 3.Print the page Actual Results: Page is not printed
Reporter | ||
Updated•16 years ago
|
Version: unspecified → Trunk
Confirmed, reproducible for me too. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008031004 Minefield/3.0b5pre OS: Windows XP
Reporter | ||
Updated•16 years ago
|
Flags: blocking-firefox3?
Comment 2•16 years ago
|
||
--> Core::Printing
Component: General → Printing
Flags: blocking-firefox3?
Product: Firefox → Core
QA Contact: general → printing
Comment 3•16 years ago
|
||
I can confirm this on Vista; a blank page comes out of my printer after a few seconds of it thinking about it.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.9?
Priority: -- → P2
One more for dholbert... can someone check to see if this happens on Linux or MacOS X?
Assignee | ||
Comment 5•16 years ago
|
||
I see this on Linux, as well. OS/Platform --> All
OS: Windows XP → All
Hardware: PC → All
Assignee | ||
Comment 6•16 years ago
|
||
Regression range: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a3pre) Gecko/20070320 Minefield/3.0a3pre Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a3pre) Gecko/20070321 Minefield/3.0a3pre Bonsai link: http://tinyurl.com/ytbw9t
Summary: Page haven't been printed if I need only a selection of words → "Print Selection" prints blank pages
Assignee | ||
Comment 7•16 years ago
|
||
I think Bug 374050 looks like most likely culprit... Maybe it's related to this comment from that checkin, which we've still got in the code: 852 // I'm leaving this in a broken state for the moment; we should 853 // be measuring/scaling with the print device context, not the 854 // screen device context, but this is good enough to allow 855 // printing reftests to work. http://mxr.mozilla.org/seamonkey/source/layout/base/nsDocumentViewer.cpp#852
Assignee | ||
Comment 8•16 years ago
|
||
(In reply to comment #7) > I think Bug 374050 looks like most likely culprit... Maybe it's related to > this comment Scratch that, we don't actually hit the code near that comment, because mIsPageMode is 0 when we get there. So, not sure which checkin would've caused this... Here's one place where we react to the "print-selection-only" setting: http://mxr.mozilla.org/seamonkey/source/layout/printing/nsPrintEngine.cpp#1896 1896 if (printRangeType == nsIPrintSettings::kRangeSelection && 1897 IsThereARangeSelection(mPrt->mCurrentFocusWin)) { 1898 adjSize.height = NS_UNCONSTRAINEDSIZE; 1899 } If I make us jump past this block (leaving adjSize.height at 63360 = 1 page-height, rather than NS_UNCONSTRAINEDSIZE), then we *almost* get correct behavior -- we print the *full lines* that contain the text selection, along with the page headers/footers. (as compared to completely blank pages in current trunk)
Assignee | ||
Comment 9•16 years ago
|
||
Ok, I've determined that the issue is this change from the patch for bug 374050: - aPresContext->DeviceContext()->GetDeviceSurfaceDimensions(width, height); + width = aPresContext->GetPageSize().width; + height = aPresContext->GetPageSize().height; The old and new code agree on the width. But in Print-Selection mode, the new code returns NS_UNCONSTRAINEDSIZE for height, and the old code returns 63360.
Blocks: 374050
Comment 10•16 years ago
|
||
Isn't this bug 402264 (there is a patch in that bug, that's been bit-rotting)?
Assignee | ||
Comment 11•16 years ago
|
||
(In reply to comment #10) > Isn't this bug 402264 (there is a patch in that bug, that's been bit-rotting)? Ah, right you are -- thanks.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•