diff --git a/controlpanel/templates/templatetags/field.html b/controlpanel/templates/templatetags/field.html index 24679be..5c1494b 100644 --- a/controlpanel/templates/templatetags/field.html +++ b/controlpanel/templates/templatetags/field.html @@ -18,11 +18,20 @@
{% if field_type == "input" %} + {% comment %} + datetime -> minute precision (Y-m-d\TH:i), not "c": a + with no `step` attribute defaults to whole-minute granularity, and a + pre-filled value carrying seconds (e.g. NewsPublishForm's `initial=timezone.now`, + live to the second) violates that step. Chrome quietly tolerates the + mismatch; Safari enforces it and refuses to submit the field at all, + with no server-side validation error to explain why -- the fix has to be + not sending a value more precise than the field claims to accept. + {% endcomment %}