Project

General

Profile

Actions

Task #41939

closed

"Retina" web logo in login and backend

Added by Felix Kopp over 11 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2012-10-12
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.0
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

The TYPO3 logos in login screen and the main logo within toolbar look blurry on retina displays. Either include vector data or at least double the size.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #49667: SpriteGenerator should be able to deal with Retina DisplaysClosedSteffen Ritter2013-07-04

Actions
Related to TYPO3 Core - Feature #68229: Render backend icon with FluidRejected2015-07-16

Actions
Actions #1

Updated by Kay Strobach over 11 years ago

this also applies to most icons in the core. As we have css sprites, we could use either conditional css:

@media all and (-webkit-min-device-pixel-ratio: 2) {
  /*Code follows here*/
}

Or webkit specific css:

.header {
   background-image: url(img/image-set-fallback-for-all-browsers-except-webkit.png);
   background-image: -webkit-image-set(
                              url(img/image-1to1.png) 1x,
                              url(img/image-1to2.png) 2x);
Actions #2

Updated by Wouter Wolters over 9 years ago

  • Status changed from New to Needs Feedback

Felix, is this fixed now?

Actions #3

Updated by Felix Kopp over 9 years ago

Now, not yet :(

Actions #4

Updated by Xavier Perseguers about 9 years ago

To me it looks like there is no problem anymore.

Actions #5

Updated by Felix Kopp about 9 years ago

Still no SVG/high-dpi logo in the backend.

Actions #6

Updated by Alexander Opitz almost 9 years ago

  • Category set to Backend User Interface
  • Status changed from Needs Feedback to New
Actions #7

Updated by Riccardo De Contardi over 8 years ago

  • Status changed from New to Closed

Closed as resolved with #52514

If you think that this is the wrong decision, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number

Actions

Also available in: Atom PDF