Bug #61656
closed
Icon size in the groupMods field not set to 16x16
100%
Description
When using high resolution icon (png) in backend modules (32x32 px) and this module can be enable/disable in the be_groups/be_users records with fields groupMods/userMods, the icon is displayed bigger than desired (see attachment).
To avoid this behaviour, I propose to introduce width and height attributes in the function "getIconHtml" of the formEngine class.
Files
Updated by Gerrit Code Review over 9 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/32812
Updated by
Updated by Gerrit Code Review over 9 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/32812
Updated by Gerrit Code Review over 9 years ago
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/32909
Updated by Anonymous over 9 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 97b928e9d5a596b029f43895f887cdeea85b7fa3.
Updated by Eric Chavaillaz over 9 years ago
If we use the first patch and modify all the method "getIconHtml" according to the new signature like Xavier said, the regression will disappear.
I can prepare a patch this evening.
Updated by Oliver Hader over 9 years ago
- Status changed from Resolved to Accepted
Changes for TYPO3_6-2 and master have been reverted.
http://forum.typo3.org/index.php/t/206216/
Updated by Eric Chavaillaz almost 9 years ago
It seems to be resolved with CSS in the TYPO3 7 version...
Thanks
Eric
Updated by Riccardo De Contardi over 8 years ago
- Status changed from Accepted to Closed
I close it for now: it has been fixed in v7 using css; It will not be fixed in 6.2 due to huge refactorings in v7, thus backporting is not straightforward.
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.