Bug 208733

Summary: Print Preview fails to respect Print -> Properties settingsf
Product: [Fedora] Fedora Reporter: morgan read <mstuff>
Component: firefoxAssignee: Christopher Aillon <caillon>
Status: CLOSED INSUFFICIENT_DATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: mcepl, mcepl, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-08-28 14:50:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description morgan read 2006-10-01 03:58:50 UTC
Description of problem:
Print Preview site to Print, choose pages to print, Print pages, get different
pages printed...

Version-Release number of selected component (if applicable):
[morgan@morgansmachine ~]$ rpm -q firefox
firefox-1.5.0.7-1.fc5

How reproducible:
Always

Steps to Reproduce:
1. Print Preview site to pint
2. Choose pages to print
3. Print selected pages
  
Actual results:
Different pages printed from those selected as per Print Preview

Expected results:
Print pages selected as per Print Preview

Additional info:

Comment 1 Matěj Cepl 2007-07-18 17:31:19 UTC
Fedora Core 5 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora Core 6, or
Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please
let us know in this bug report.  If after a month's time we have not heard back
from you, we will have to close this bug as CANTFIX.

Setting status to NEEDINFO, and awaiting information from the reporter.

Thanks in advance.


Comment 2 Matěj Cepl 2007-08-28 14:50:07 UTC
We haven't got any reply to the last question about reproducability of the bug
with Fedora Core 6, Fedora 7, or Fedora devel. Mass closing this bug, so if you
have new information that would help us fix this bug, please reopen it with the
additional information.