Yes, when sorting by date it's currently configured to disable typo-tolerance. This is to avoid having an old (but approximative, with typos) result BEFORE the correct ones.
Ah the old multi-factor sort problem. Fun figuring out how to handle those scenarios in Elastic Search too (or more generally any sorting UI). For example you want traditional Chinese food near you. What is better - traditional Chinese food 14km away or fusion 2km away? Well that depends on the wetware, but you have to guess what the user would want.