Web page content not printing at extremetech

NEW
Unassigned

Status

()

Core
Printing: Output
6 years ago
6 years ago

People

(Reporter: Nick, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20100101 Firefox/6.0.2
Build ID: 20110902133214

Steps to reproduce:

Go to this web page: http://www.extremetech.com/computing/95599-is-the-opposition-still-unified-regarding-unity


Actual results:

the content of the first two pages will not print nor show up in print-preview. 


Expected results:

The content should be printable. I had to use Google Chrome to print the content :(

Updated

6 years ago
Component: General → Printing: Output
Product: Firefox → Core
QA Contact: general → printing
Version: 6 Branch → Trunk

Comment 1

6 years ago
Created attachment 560499 [details]
Zip of Saved Page as Web Page Complete

Able to confirm on Mozilla/5.0 (Windows NT 5.1; rv:9.0a1) Gecko/20110915 Firefox/9.0a1 ID:20110915030845
It's at least partly due to this chunk in style.css:
================
/*------ twocolumns ------*/
.twocolumns{width:984px;overflow:hidden;border-top:1px solid #e4e4e4;background:url(images/bg-twocolumns.gif) repeat-y;margin:0 auto;padding:0 7px 0 1px}
================

If I remove "overflow:hidden" from that list, it fixes the issue.

In the not-too-distant-past, I would have duped this to bug 129941, but that bug's now resolved. :)  bz, do you know if there are still existing bugs on us cropping printouts when overflow:hidden is set?
(btw, I can repro on Mozilla/5.0 (X11; Linux x86_64; rv:9.0a1) Gecko/20110915 Firefox/9.0a1 )
OS: Windows XP → All
Hardware: x86 → All
Status: UNCONFIRMED → NEW
Ever confirmed: true
> bz, do you know if there are still existing bugs

Not offhand, modulo discussion in bug 609227...

Clearly _something_ is broken here, though.
(See also bug 588288, which is also an overflow:hidden-dependent printing truncation bug.)
You need to log in before you can comment on or make changes to this bug.