Insane. Our discussion here reminds me of something that took place on the Apple forum beginning in the fall of 2013 about an incredibly frustrating bug that emerged with the introduction of iOS 7.0 that drove the people like me who first noticed it crazy. We couldn't figure out several things about the problem: (1) if it affected only a certain segment of the population running iOS 7 and if so if it was dependent on some slightly different version of their hardware or maybe some obscure software flag that users had no access to; (2) why Apple wasn't addressing the glaring problem; (3) why there weren't more people noticing it and journalists writing about it. Eventually the thread grew to 1,022 replies (I wouldn't be surprised if it's one of the largest on the forum) and is still ongoing. The issue never got acknowledged by Apple and was never addressed, and still lives on for some people on some devices in all subsequent versions of the OS.
I don't think that fate could befall this issue, as it seems fairly simple and isolated to one particular and limited function, so I can't imagine it would be that difficult to fix. I think it just needs to be brought to the attention of some Apple managers, though back in 2013 we couldn't got any relief even after dozens and possibly hundreds of us sent explanations of the problem we were having using the /feedback form Apple offers. I don't know what you have to do to get them to genuinely pay attention to even an obvious and egregious bug like this. (The other one from 2013 was way worse.)
I am convinced this will eventually get fixed, but I would not make any bets as to when.