or i could argue that an issue 90% of people will run into is a higher priority than one 2% of people will run into
or i could argue than the risk of accidentally opening something you didn't want to is higher than the risk of losing unsaved work
the reason foss sucks when it comes to ux is this attitude of insisting that ux problems are somehow some "other" category of problem, rather than an engineering constraint that needs to be designed around like every other one
case in point, for some reason you're still refusing to acknowledge that they're both ux problems. and if you do, your original reply ceases to even make sense.
if you aren't refusing to acknowledge they're ux problems, you're saying it's unhelpful to call them what they are, which is obviously nonsense
and again, sane defaults are ux