Closed Bug 54092 Opened 24 years ago Closed 23 years ago

Xprint uses one bitmap in place of all bitmaps on page

Categories

(Core Graveyard :: Printing: Xprint, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.1

People

(Reporter: tlogue, Assigned: roland.mainz)

References

Details

(Whiteboard: [rtm-])

In printing a complex web page such as usatoday.com, one bitmap image is being 
used in place of each of the bitmaps that exist on the page.
dcone - I'm default owner of XPrint component. If you can confirm this is xprint
specific
problem, please assign the bug to tajima@eng.sun.com.
I've verified this does not happen with Mozilla-M17/Windows, so it doesn't seem 
like it could be a layout engine error.  As requested, I'm reassigning to 
tajima@eng.sun.com.
Assignee: dcone → tajima
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
This is needed.  Hidetoshi, can you estimate the work involved?  
Keywords: rtm
Target Milestone: Future → ---
dougt, why this is needed for rtm ?
ftang, IIRC this is a blocker for embedding work according to ThomasVL per 
recent conference call. ThomasVL, please provide whatever additional details you 
can about why this matters within a public bug report. In the meantime, ftang, 
this must be fixed in the RTM timeframe.

petitta: I think this is one of the four bugs that were discussed on Friday, 
yes?
we got a producted based to gecko that includes printing on some non PS devices, 
to do this, it uses XPrint.  Since the one image is used for all page images, you 
don't get the expected output.  (yes, the print code will hopefully end up as OSS 
in the end).
I don't think I can fix this in time for rtm time frame. Reassign to Frank
Petitta for now
as he's willing to look for another engineer.
Assignee: tajima → petitta
Status: ASSIGNED → NEW
Will the engineer assigned to this bug please contact petitta@netscape.com ASAP
Assignee: petitta → dcone
I don't have anything to do with xprint.  I don't even have a linux (unix) box 
to work on.  Giving back to petitta.
Assignee: dcone → petitta
Reassigning to waqar.
Assignee: petitta → waqar
Marking [rtm need info]
Whiteboard: [rtm need info]
Whiteboard: [rtm need info] → [rtm-]
PDT marking [rtm-]. Doesn't seem severe enough to hold N6 RTM for, but of course
that's independent of embedding needs.
For the record this is an embedding priority, not a Netscape 6 RTM priority. The
[rtm-] marking won't stop this from being checked in on the trunk or in any
other place it may need to be checked in; it only prevents checkin on the N6 RTM
branch, where this isn't needed anyway.
Gents, Where do we stand on this.  Could I please get an updated status ASAP?
The status I got from Jay Hobosn is that, he is modifying the Xprint library to 
be able to set the resolution for printing. He also has some more fixes that he 
is checking into Xprint.
spam : changing qa to sujay (new qa contact for Printing)
QA Contact: shrir → sujay
SPAM: Changing component from "Printing" to "Printing: Xprint"
SPAM: Sorry, 2nd attempt... ;-((
Component: Printing → Printing: XPrint
Setting milestone to future.
Target Milestone: --- → Future
Reassigning to xprint owner
Assignee: waqar → katakai
QA Contact: sujay → Roland.Mainz
katakai... do you have any idea when Sun will have a fix for this available ?
Overtaking... fix for this seems to be easy and will be fixed with other Xprint
image related stuff in bug 78548...
Assignee: katakai → Roland.Mainz
Depends on: 78548
QA Contact: Roland.Mainz → katakai
Accepting...
Status: NEW → ASSIGNED
Target Milestone: Future → mozilla0.9.1
Depends on: 77210
let's land this in 0.9.2. let drivers know if this creates problems. thanks.
Target Milestone: mozilla0.9.1 → mozilla0.9.2
This bug has been fixed by patch in bug 77210.
patch appiled to both 0.9.1-branch and trunk.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Target Milestone: mozilla0.9.2 → mozilla0.9.1
Verified.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.