Bernard Siebens
5d3dbebd77
<input type=datetime-local> with no step attribute defaults to whole-minute granularity, but the value was rendered via the "c" filter (full ISO, always includes seconds) -- NewsPublishForm's initial=timezone.now made every render carry live, non-zero seconds, which violates that implicit step. Chrome tolerates the mismatch; Safari enforces it and silently refuses to accept the field, with no server-side validation error to explain why. Format datetime-local values at minute precision instead. Fixes every field using this widget (event start/end/gathering/deadline, series dtstart/until), not just the one this was noticed on. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>