#68303Image width/height are displayed as 0 in backend for default dimensions
Description
When editing a textpic element in backend, in the tab “Appearance” under “Image Adjustments”, width and height are displayed as 0 if no custom size has been chosen. This can be confusing to users, as the images are actually rendered at their full size in the frontend (and are not invisible as the displayed dimensions might suggest).
In TYPO3 versions prior to 6.2.12, the text fields were empty instead, which makes more sense from a user perspective. This change was triggered by commit:34dd11835be8097c259b4f83e153cddf46dab2b0 in response to #65965.
Reviews 2
Related issues 3
History 1723
-
Markus Klein commented and changed status
NewAccepted priority-- undefined --Must have target version Complexity medium Sprint Focus On Location Sprint 07/18/15, 14:50 -
Helmut Hummel commented 07/20/15, 15:46
Markus Klein wrote:
> I agree that the situation is not optimal. Unfortunately, FormEngine is not very flexible and the original fix is actually important for many other integer fields, where zero is just a valid number.
>
> We would have to add NULL handling for the width and height fields, which would mean a DB change. That is not feasible for a released version.
> Of course we should fix that for CMS 7.Uhm, to me it seems that the original fix must not have gone into 6.2, right?
That is quite a big change in behavior for image size fields. -
Markus Klein commented 07/20/15, 20:20
The 6.2 fix is ok to my opinion since it improves the situation for many other integer fields. width/height should have a NULL value to indicate “use default”.
This can’t be changed on 6.2 though. -
Markus Klein changed priority
Must haveShould have target version Complexitymediumhard Sprint FocusOn Location SprintStabilization Sprint 07/29/15, 19:37 -
Markus Klein commented and changed priority
Should haveMust have target version Sprint FocusStabilization SprintRemote Sprint 07/29/15, 23:15Christian and me talked about this and took a deeper look into the code. Unfortunately we can’t get that right for all cases in 6.2.
We need to fix this on master though.
-
Mathias Brodala commented 09/13/15, 17:24
Still valid with the current 7.5-dev
-
Benni Mack changed target version 09/24/15, 20:44
-
Andreas Kienast commented and changed target version 10/29/15, 12:37
After talking with Christian we decided to postpone this ticket to CMS 8.
-
Benni Mack changed target version 05/04/17, 17:48
-
Oliver Hader commented and changed status
AcceptedNeeds Feedback Tags pending-close 12/04/20, 16:27Is this still a topic in TYPO3 v9 / v10?
-
Oliver Hader changed Is Regression
10 12/04/20, 16:27 -
Riccardo De Contardi commented 12/25/20, 23:22
The issue is still present on 11.1.0-dev
-
Christian Kuhn changed status
Needs FeedbackNew 02/19/22, 12:29 -
Gerrit Code Review pushed patch set 1 for main to change 85156 status
NewUnder Review 07/08/24, 18:32 -
Gerrit Code Review pushed patch set 2 for main to change 85156 01/20/25, 19:20
-
Gerrit Code Review pushed patch set 3 for main to change 85156 03/30/25, 08:56
-
Gerrit Code Review pushed patch set 4 for main to change 85156 03/30/25, 18:15
-
Gerrit Code Review pushed patch set 5 for main to change 85156 03/30/25, 19:36
-
Gerrit Code Review pushed patch set 6 for main to change 85156 04/01/25, 13:15
-
Georg Ringer commented and changed status
Under ReviewResolved done0 %100 % 04/07/25, 14:20Applied in changeset commit:7aa77511a7bb0c9e061700360991229f7f7f200a.
-
Oliver Bartsch changed Related to #106576 04/16/25, 08:51
-
Benni Mack changed status
ResolvedClosed 08/12/25, 14:35 -
Markus Klein changed Related to #110195 07/14/26, 10:49
I agree that the situation is not optimal. Unfortunately, FormEngine is not very flexible and the original fix is actually important for many other integer fields, where zero is just a valid number.
We would have to add NULL handling for the width and height fields, which would mean a DB change. That is not feasible for a released version.
Of course we should fix that for CMS 7.