Currently LocalDateDeserializer automatically accepts non-standard format where time part also exists.
While this is useful for some use cases, compatibility, it seems reasonable that if user forces "strict" handling (via @JsonFormat, or global default), that part would not be accepted. This is in line with similar handling on LocalDateTimeDeserializer, with respect to handling of non-compliant timezone (Z) suffix.