Bug #19044

typo3 logo in backend on top left looks not perfect because it has white background on gradient background

Added by Cyrill Helg over 13 years ago. Updated over 11 years ago.

Should have
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


Wouldn't it look better if the logo would have the same gradient background as the top bar in backend? Maybe you need to adjust your monitor to see the issue:


(issue imported from #M8875)


typo3_logo_ugly.png (1.94 KB) typo3_logo_ugly.png Administrator Admin, 2008-07-01 20:33
typo3logo_mini.png (1.62 KB) typo3logo_mini.png Administrator Admin, 2009-06-13 12:01

Updated by Chris topher about 13 years ago

Can you provide a modified version of the image?


Updated by Cyrill Helg over 12 years ago

The image should be transparent, do you agree?


Updated by Cyrill Helg over 12 years ago

That one should do the trick :)


Updated by Chris topher over 12 years ago

Hey Cyrill,

does this picture have exactly the same background color as the bar in the backend does?

If so:
To get your patch included, send it to the TYPO3-core-list!

Check out:


Updated by Steffen Kamper over 12 years ago

committed logo from Johannes to trunk, rev 5585


Updated by Cyrill Helg over 12 years ago

I don't think thats fixed in 4.2.9, the image has no transparency.

The image I supplied had transparent background which should do the trick...


Updated by Chris topher over 12 years ago

Right Cyrill, this is fixed in TYPO3 4.3, e.g. in the current beta.
As Steffen wrote, your fix has been applied.

But it was not fixed in 4.2, because in a branch (like 4.2), only bugs are fixed.


Updated by Cyrill Helg over 12 years ago

Yes I see, but in my opinion this is a bug... so it should be fixed in branch as well.


Updated by Chris topher about 12 years ago

Hi Olly, traget-version should stay 4.3.0, because it is fixed there.

Furthermore, I don't think that this minor issue will/should be changed in 4.2; also because 4.3 will be released soon.

I would call this fixed.


Updated by Benni Mack about 12 years ago

As this is fixed in the most recent stable version and there is very very little chance that this gets fixed in 4.2.x, I'm suggesting to close this bug.

Also available in: Atom PDF