throw away nsImageGTK client side copy

RESOLVED FIXED

Status

()

Core
XUL
RESOLVED FIXED
16 years ago
16 years ago

People

(Reporter: tor, Assigned: tor)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

16 years ago
Patch throws away client side copy on Optimize().  Postscript printing now
does a LockImagePixels(), which will read back the data from the server if
the image has been optimized.
(Assignee)

Comment 1

16 years ago
Created attachment 71086 [details] [diff] [review]
throw away client side image copy
Comment on attachment 71086 [details] [diff] [review]
throw away client side image copy

r/sr=blizzard
Attachment #71086 - Flags: superreview+
(Assignee)

Comment 3

16 years ago
Created attachment 71116 [details] [diff] [review]
as above, plus kill the black background of transparent images
Attachment #71086 - Attachment is obsolete: true
(Assignee)

Comment 4

16 years ago
Black printed background, that is.

Comment 5

16 years ago
Comment on attachment 71116 [details] [diff] [review]
as above, plus kill the black background of transparent images

r=pavlov
Attachment #71116 - Flags: review+
Comment on attachment 71116 [details] [diff] [review]
as above, plus kill the black background of transparent images

sr=blizzard
Attachment #71116 - Flags: superreview+

Comment 7

16 years ago
a=chofmann for 0.9.9
(Assignee)

Comment 8

16 years ago
Checked in.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED

Updated

16 years ago
Attachment #71116 - Flags: approval+
Hrm.  It looks like this actually slowed down page load times on btek by about
10 ms.  Any ideas why?
(Assignee)

Comment 10

16 years ago
No idea - all it does it add a few delete[]s when images finish loading.
What's the space tradeoff here?  It's signifigant, right?
You need to log in before you can comment on or make changes to this bug.