Is this a bug they are working on I wonder?
I suspect it is a bug - or at least an oversight - rather than a deliberate change.
Ancestry user trees usually have at least one bug at any given time and they tend to be resolved. A couple of years ago there was a bug with custom sources that caused external web links to be garbled, rendering them useless. That lasted a couple of months, I think, and was a major impediment to my usual workflow.
I've raised this issue on the Ancestry Users facebook group and Ancestry rep Crista Cowan frustratingly suggested a workaround - as if the way I enter the info is correct - rather than acknowledging the problem.
It's because all the dates are in a different format.
If you want them in the correct order, when saving to your tree, I always change the date of death to the 1st of the month in which the burial happened and the residence date to the last day of the previous month and hey presto they are in the correct order. And if you always use the 1st and 30/31st then you will know that it is a manually amended date.
Pheno