#109682FormEngine datepicker fields are displayed broken
Description
When editing a date field, this display error occurs when clicking starttime or endtime
This happens in Chrome(147) and Firefox(150.0).
Reviews 3
Related issues 1
Files 1
History 1115
-
Nico Huber changed category <span data-processor="relativetime" data-value="2026-04-22T08:46:26+00:00" > 04/22/26, 08:46 </span>
-
Josef Glatz commented and changed priority
Should haveMust have <span data-processor="relativetime" data-value="2026-04-22T14:24:08+00:00" > 04/22/26, 14:24 </span> -
Garvin Hicking commented and changed status
NewAccepted Is Regression 1 <span data-processor="relativetime" data-value="2026-04-22T16:38:13+00:00" > 04/22/26, 16:38 </span>Can confirm – happens in all of Formengine datepickers. Might be related to https://review.typo3.org/c/Packages/TYPO3.CMS/+/93756
-
Garvin Hicking changed Related to #109654 <span data-processor="relativetime" data-value="2026-04-22T17:25:45+00:00" > 04/22/26, 17:25 </span>
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2026-04-22T18:04:07+00:00" > 04/22/26, 18:04 </span>
OK so at first I was able to reproduce that with my checkout. I then reverted the patch https://review.typo3.org/c/Packages/TYPO3.CMS/+/93756. Then I reloaded my browser and the issue was gone, so I was sure this commit would be responsible.
However, then I checked out the latest version AGAIN, cleared my cache, and – it still worked. And now I can no longer reproduce the error.
So: Could you try to purge your browser cache? Did you run a previous 14.2 installation probably? Maybe some CSS asset got cached and was not yet reloaded.
-
Nico Huber commented <span data-processor="relativetime" data-value="2026-04-22T18:17:20+00:00" > 04/22/26, 18:17 </span>
I first installed version 14.3. I cleared the entire browser cache and all TYPO3 caches, but the problem persists.
After I opened the developer tools in the browser and reloaded the page, the problem was gone. If you close the developer tools again and reload the page, the problem reappears.Edit: If you open the developer tools in the browser, the issue is resolved for that browser session. If you log in using incognito mode without opening the developer tools, the issue persists.
-
Garvin Hicking commented and changed subject
Browser date field display bugFormEngine datepicker fields are displayed broken <span data-processor="relativetime" data-value="2026-04-23T06:26:04+00:00" > 04/23/26, 06:26 </span>Thanks for that detail, now I can reproduce it again, and also say for sure that reverting `d02c8927fdf27377bcbf9272f1c7e7c78e9b3b43` fixes it.
-
Gerrit Code Review pushed patch set 1 for main to change 93813 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2026-04-23T07:03:58+00:00" > 04/23/26, 07:03 </span> -
Gerrit Code Review pushed patch set 2 for main to change 93813 <span data-processor="relativetime" data-value="2026-04-23T07:12:37+00:00" > 04/23/26, 07:12 </span>
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2026-04-23T11:49:00+00:00" > 04/23/26, 11:49 </span>
Benjamin created the patch attached, are you maybe able to verify that this fixes your issue as well?
-
Nico Huber commented <span data-processor="relativetime" data-value="2026-04-23T12:34:56+00:00" > 04/23/26, 12:34 </span>
Yes, the patch has fixed the problem
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 93836 <span data-processor="relativetime" data-value="2026-04-24T08:32:10+00:00" > 04/24/26, 08:32 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 93813 <span data-processor="relativetime" data-value="2026-04-24T14:22:28+00:00" > 04/24/26, 14:22 </span>
-
Benjamin Franzke commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-04-27T06:20:10+00:00" > 04/27/26, 06:20 </span>Applied in changeset commit:7b121e4522637a9fe56d636a37c1daf339d5b8c7.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-08-11T08:46:52+00:00" > 08/11/26, 08:46 </span>
This problem can be reproduced also within ext:scheduler