Short question. When USE_TZ is set to true, the framework prepares the datetime into a timezone aware string for use in json, but also for use in the HTML interface. This results in an HTML input tag with a value that includes the timezone offset, for value="1978-12-28T19:00:00+01:00", but datetime-local does not officially support a timezone. Firefox 'works', it just displays the string with timezone part. Chrome fails, it leaves the input field empty.
Since datetime-local should not include a timezone, I suppose this is a 'bug' in the Django REST framework. Or maybe I'm doing something wrong? Anyone encountered this problem? -- You received this message because you are subscribed to the Google Groups "Django REST framework" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-rest-framework+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-rest-framework/6b84f317-84fc-48eb-a01a-47cd5338e67en%40googlegroups.com.
