All of this is thankfully resolved by the spec choice to stick to a specific ISO string format for the value property.
You are talking about locale-dependent formats - which is why the value property of the input element conforms to ISO 8601 YYYY-MM-DD and guarantees that the values are predictably sortable.
There is no other meaningful ordering of dates other than sorting chronologically.
HTMLInputElement with type=date honestly does everything right given the constraints.
As said, this post is a valid complaint about mobile native UI, no less no more.
You are talking about locale-dependent formats - which is why the value property of the input element conforms to ISO 8601 YYYY-MM-DD and guarantees that the values are predictably sortable.
There is no other meaningful ordering of dates other than sorting chronologically.
HTMLInputElement with type=date honestly does everything right given the constraints.
As said, this post is a valid complaint about mobile native UI, no less no more.