#110245Backend datetime picker opens at 0×0 in Firefox 140.12.0esr (64-Bit)
Description
*Subject*
FormEngine datetime picker (flatpickr popover) opens at 0×0 / invisible in Firefox ESR
TYPO3 v14.3.5
PHP 8.4.18
EXT:news v14.0.3
Firefox 140.12.0esr (64-bit)
*Description*
The backend FormEngine datetime picker (type => ‘datetime’) renders its flatpickr calendar as a popover. In some cases in Firefox 140 ESR the popover does open, but with a height and width of 0, so it is not visible.
We have multiple v14 projects where this happens. Tested with EXT:news v14.0.3: the starttime & endtime datepickers are visible and work, while datetime & archive are not visible, even though they use the exact same TCA config. I’m not 100% sure, but I don’t think this is related to EXT:news itself, it feels more like something in the core.
I tried to debug it with the help of Claude Code, which gave me the following snippet that I ran in a Firefox ESR browser:
(() => {
const els = [...document.querySelectorAll('typo3-formengine-element-datetime')];
return els.map(el => {
const fp = [...el.querySelectorAll('input')].map(i => i._flatpickr).find(Boolean);
if (!fp) return { field: el.getAttribute('recordfieldid'), flatpickr: false };
const cal = fp.calendarContainer;
let err = null;
try { fp.open(); } catch (e) { err = e.name + ': ' + e.message; }
return {
field: el.getAttribute('recordfieldid'),
openedPopover: cal.matches(':popover-open'),
display: getComputedStyle(cal).display,
rect: JSON.stringify(cal.getBoundingClientRect()),
error: err
};
});
})()
This produced the following result:
| _.Field | _.openedPopover | _.display | _.rect (w x h x,y)|
|datetime|true|block|0 x 0 (0,0) |
|---|---|---|---|
| archive | true | block | 0 × 0 (0,0)|
|starttime|true|block|280 × 374 (24, 428) |
| endtime | true | block | 280 × 374 @ (377, 428) |
So it seems the popover renders, but with a size of 0×0. Claude suspected that CSS Anchor Positioning might be the cause, but the CSS snippet it suggested as a fix did not work. So I’m not sure whether this is really the right track. I’m just sharing the observations here, the actual cause is probably better judged by someone who knows the FormEngine internals.
Steps to reproduce- Use Firefox ESR 140
- Edit any EXT:news record (fields datetime, archive on the first tab; starttime, endtime in the Access palette).
- Click a datetime field to open the calendar.
Reviews 1
Related issues 1
History 35
-
Gerrit Code Review pushed patch set 1 for main to change 95157 status
NewUnder Review <span data-processor="relativetime" data-value="2026-08-06T22:05:18+00:00" > 08/06/26, 22:05 </span> -
Gerrit Code Review pushed patch set 2 for main to change 95157 <span data-processor="relativetime" data-value="2026-08-07T13:38:26+00:00" > 08/07/26, 13:38 </span>
-
Benni Mack changed status
Under ReviewClosed <span data-processor="relativetime" data-value="2026-09-04T09:29:08+00:00" > 09/04/26, 09:29 </span> -
Garvin Hicking changed Related to #110406 <span data-processor="relativetime" data-value="2026-09-15T09:52:59+00:00" > 09/15/26, 09:52 </span>
hey Tobias,
- Firefox ESR 153.0esr has full support
- Devices that cannot upgrade to Safari 26 are at least 7 years old
We once defined “modern browsers” as evergreens, all features were supported by the upstream browsers on day of release, that version is intended to be supported.