162764 - change theme button maps from gif formats to png to retain their bit depth

Status: RESOLVED EXPIRED

(SeaMonkey :: Themes, defect)

Description

[marlon bishop]

The problem is a visual regression since netscape 6.23.  When we streamlined
themes by using button maps, instead of individual files, we lost God knows how
much of the modern button color gamut by limiting all buttons to one 256 gif
color palette.  We should have used PNG8, which would have retained full color
(actually then button colors would have been even more accurate than in Netscape
6.23)

If i post all of the toolbar buttons in png8 format, does anyone have a tool or
script for automating the insertion of seperate files into the button grid?

Comment 1

[marlon bishop]

actually, insert png24 everywhere i said png8

Comment 2

[marlon bishop]

Attachment: image showing the difference in quality

look at the banding happening in the toolbar area, and also in the green arrow
indicators which is pretty severe.   when zoomed out the net effect of this for
users is a loss of 3d depth and color brilliance.

Comment 3

[Ben Bucksch (:BenB)]

"The image “http://bugzilla.mozilla.org/attachment.cgi?id=95324&action=view”
cannot be displayed, because it contains errors." says my build.

Comment 4

[Stefan Borggraefe]

Same here. I can view the image with The Gimp and Eye Of Gnome (eog) without any
problems but Mozilla just displays the error message. After just opening and
saving the image with The Gimp it can also be displayed with Mozilla.

I'm going to attach the image fixed the described way.

Stefan

Comment 5

[Stefan Borggraefe]

Attachment: image showing the difference in quality (fixed for mozilla)

Comment 6

[marlon bishop]

sorry about the errors, i couldn't figure it out.  only some builds seem to have the problem.  
Photoshop and Preview open it fine.

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420