242423 - The about:logo should use alpha channel for anti-aliasing.

Status: RESOLVED DUPLICATE of bug 299897

(SeaMonkey :: Themes, defect)

Description

[Thorsten Huber]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

When choosing a different default background colour than white, the
anti-aliasing of the Mozilla "about:" logo doesn't work. Suggestion: Use PNG
format with alpha channel for anti-alias.

Reproducible: Always
Steps to Reproduce:
1. Choose e.g. black as background colour in prefs, appearance, colours.
2. Open the "about:" website.
3. Watch the border of the logo.

Actual Results:  
White artifacts appear at the logo's border.

Expected Results:  
It should make a smooth transition to black.


I've made an attempt to create an alpha mask with mediocre results, perhaps
someone else can do better?

Comment 1

[Thorsten Huber]

Attachment: Sample image, don't use this.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Not really a browser bug, but I'm not sure where it should go.... mozilla.org?

Comment 3

[Thorsten Huber]

Attachment: mozilla_logo.png

This attempt is a lot better, though the black border line around the logo is a
bit thinner than in the original GIF image.

Comment 4

[Thorsten Huber]

Attachment: mozilla_logo_test.png

Only submitting this for completeness. It's an attempt to fix the thin border
problem with the previous logo, however the quality is still lacking compared
to the original image (about:logo).

Comment 5

[Thorsten Huber]

After submitting this, I noticed another bug in the original logo:
The eyes and teeth are partially transparent instead of white, so if you set the
background to e.g. blue, "Godzilla" gets blue teeth and eyes.

Comment 6

[Jesiah S]

*** Bug 250607 has been marked as a duplicate of this bug. ***

Comment 7

[Jesiah S]

David Baron moved bug 250607 to XP Apps: GUI Features maybe that is where this
bug belong.

Comment 8

[Thorsten Huber]

Are you sure? It looked to me as if the bug was put into this component from the
beginning, and David saying it does *not* belong there.

Um... could someone edit the bug for me, Bugzilla always says I wasn't the
submitter for some reason.

Component: Themes
QA: [e-mail]
Priority: P5
Target Milestone: mozilla1.8beta
Reassign to: [e-mail]

Comment 9

[Thorsten Huber]

I managed to change component and QA, but I cannot change priority, target
milestone, confirm or reassign to "[e-mail]". Bugzilla says:

"only the owner or submitter of the bug, or a sufficiently empowered user, may
change that field"

 :shrugs: 

Comment 10

[Thorsten Huber]

You know what, the 2nd attempt (mozilla_logo_test.png) doesn't look that bad.
Someone with power put this into the source please? It's not 100% perfect as I'm
not a graphics artist, but it's better than having anti-aliasing for white back
ground only.

Comment 11

[Thorsten Huber]

Attachment: transparency removed (white background)

Another, quite simple solution: Simply turn off transparency altogether.
Inspired by the Firefox rectangular logo.

Comment 12

[Peter Kovář]

What about SVG logo instead of bitmap image?

Comment 13

[timeless]

[e-mail]: you want us to ship with an image that doesn't work in
most builds? that sounds like a great idea.

Comment 14

[Peter Kovář]

Not exactly. I mean let PNG logo as it is now and add (or replace with) SVG logo
for SVG enabled builds. Is that too crazy?

Comment 15

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 16

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.