


@JacobDrummond thank you for your report.
This issue was fixed in developer branch but was not fixed in 2.1 yet.
We have internal ticket for this version: MAGETWO-57839
@veloraven, thanks for your feedback.
When will these develop fixes be included in a release?
In general, what is your develop-to-release workflow?
@JacobDrummond It can happen because of locale: try M/D/Y format instead and check if it works.
@webdevlabo, yes that's the known fix :)
The whole point of this bug report is that Magento should be implementing locale consistently across JS and PHP.
@veloraven this has been reported a few times since October, do you have an ETA on when it might be fixed? or is there a way we can see the code that needs to be modified from the developers branch?
We are based in UK with latest Magento 2.1.3, is there an update on when the fix will be released?
@veloraven I performed the tests and the error persists in versions 2.1.5 and 2.1.6
I opened an issue #9432
@JacobDrummond, thank you for your report.
The fix for this issue is already available in the develop and 2.2-develop branches. See commits with MAGETWO-57835 in the title.