Closed Bug 539703 Opened 15 years ago Closed 14 years ago

Whenever I try to print from Confluence (which I believe contains frames) and use Firefox, only the first page prints.

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: rlee, Unassigned)

Details

(Whiteboard: [CLOSEME 2011-1-30])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)

Whenever I try to print a multi-page document from Confluence (which I believe contains frames) using Firefox, only the first page prints. (Only the first page is visible in the print preview also.) This does not happen in IE, which makes me think that it's a Firefox issue, not a Confluence (Atlassian) issue. 

Reproducible: Always

Steps to Reproduce:
1. Locate a web page with frames and multiple pages.
2. Open a print preview for the page.
3. Only one page is visible.
Actual Results:  
See my Details comments.

Expected Results:  
All pages should print.

Everyone where I work is complaining about this issue. It would be great it you guys would fix it.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.