Ping @MaxSem as the author. This is probably a quick fix and would be highly appreciated. Sad to hear that the Wikimedia team is lacking resources to fix such rather easy but annoying bugs.

Alright, thanks for getting that right, did not find that issue on a quick search.

Ping to @jeremyb as I saw your activity on https://phabricator.wikimedia.org/T66281 and this seems to be somehow the same with its ability to produce data loss. However I have to say that the user will probably be warned by the diff displayed.

In T165283#4032005, @Deskana wrote:

This represents a fundamental misunderstanding of how prioritisation works. Firstly, it is a mistake to try guessing how difficult a bug is to fix. How simple bugs seem to you or I often does not correspond to the engineering difficulty. Secondly, how easy or hard something is to fix is only one of many factors which affect the prioritisation of a task. My team does not have the time to fix every bug that is reported, even if people make guesses that they're easy. This means that very valid bugs get put in the backlog.

In T165283#4029050, @Deskana wrote:

Yes, there are resource limitations, and that means that we have to say no to a lot of things, and that even very valid bugs like this one can not always be worked on. It's a bit mean to call that "wrong priorities/management". I try my best.

I guess there is an underlaying lacking manpower, maybe combined with wrong priorities/management on the developer/bug team side :)

@Tkarcher Thanks. Also I think that one has a chance to see the problem in the diff-view before saving, right? But nonetheless this should be fixed.

Commenting to give this more relevance. Also: Is there a warning that there are changes that will be overwritten?

Just adding a comment to (hopefully) give this more relevance.

@Deskana I was referring to what @Jdforrester-WMF wrote. He was only referring to space problems he mentioned.

@Jdforrester-WMF Well, at least for me there seems to be plenty of space. So why not detect the screen size and then add the button if there is space (responsive design)?

Is there any update on this?