Comment 6 for bug 729056

I originally experimented with fixing this bug, but never commented back here. My fault.

This should not have been fixed. We can reliably format a date into a locale-specific display string. But as far as I recall, there is no way to either:
A) Programatically format a locale-specific display string back into a date
B) Or programatically query what the locale-specific display string breaks into (i.e. is "%x" really "%y-%m-%d"?)

So if we show the data in the locale-specific way, there's no way to parse it back again, when the user edits the text box. This merge has made it so that when the user tries to manually edit the date box, it will screw up the date.

I've filed bug 1149696 about this.