Closed Bug 328639 Opened 20 years ago Closed 14 years ago

Only the frame prints; the content does not. On Safari the entire page prints fine.

Categories

(Core :: Printing: Output, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: stowne, Unassigned)

References

()

Details

(Keywords: qawanted, Whiteboard: [closeme 2011-03-15])

Attachments

(1 file, 1 obsolete file)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0 Only the frame prints; the content does not. On Safari the entire page prints fine. Reproducible: Always Steps to Reproduce: 1.Just try to print this page 2. 3. Actual Results: Only the frame (or you could call it the top heading) prints. The contents does not.
This is the URL that won't print properly on Camino but will print fine on Safari.
Firefox has the same behavior, so -> core
Assignee: mikepinkerton → printing
Product: Camino → Core
Version: unspecified → 1.8 Branch
Attached file Somewhat shortened testcase (obsolete) —
THIS BUG MAKES NO SENSE AT ALL. Things of note: 1. The exact text of the <select> matters. If you remove the ] from the end, the bug is still there. If you switch the L at the front for an x, the bug is still there. However, if you switch the ] for an x, the bug is gone. 2. Padding matters. Removing style="padding:blah" from anywhere makes the bug vanish, and removing extra nested tables makes the bug vanish, presumably because tables have default cellpadding. 3. Huge, sweeping changes have no effect at all. One of the things I changed while making the testcase was switching it from a single, fixed-width column to letting it take up as much of the screen as it needed. That had no effect. In short, I'm completely confused.
OS: MacOS X → All
Hardware: Macintosh → All
Version: 1.8 Branch → Trunk
I managed to pull a few more things out of the testcase... it still gives no clue what the actual problem is.
Attachment #213249 - Attachment is obsolete: true
Keywords: qawanted
Reporter, your bugfile needs a *_reduced_* testcase, a *_minimized_* testcase. I underline here reduced and minimized. What is a Simplified Test Case, and How Do I Make One? http://www.mozilla.org/newlayout/bugathon.html#testcase Also, your description needs to define exactly what are the expected results: in other words, what is supposed to be printed. Finally, "be sure that you've reproduced your bug using a build released within the past three days. Our development process moves at lightning speed, and the bug you've found may already have been fixed." Bug Writing Guidelines http://www.mozilla.org/quality/bug-writing-guidelines.html
Gérard, the testcase for this is very hard to make. It depends on strange interactions between things with only a few pixels tolerance for change. It's not feasable to ask someone inexperienced to do it; I've been doing them for years and it took me a long time to reduce it even as far as I did. Also, as I understand it end users aren't expected to use nightly builds to file bugs, only the latest release build--which Camino 1.0 is.
Assignee: printing → nobody
QA Contact: printing
do you see this issue still with version 3.6 or 4.0 beta?
Whiteboard: [closeme 2011-03-15]
Testcase prints correctly for me in FF 4.0.1 Mac.
wfm per comments, no other respose to request for additional info so incomplete otherwise
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: