It would have been better to finish this conversation on a positive note without dissecting and belabouring it, which we now are doing - regrettable.
At the point where I took it on the chin that my earlier comment was obnoxious, it should have been left there (how often does a person even get that far!).
It’s a shame we could not have left well alone at that point. This thread is not at all the appropriate place for raising anyone’s broader issues with me being “an insulting person” (or issues with anyone for that matter).
Now I feel forced to point out that this self-righteous “the app said it is a bug” business is wrong - which is all that I actually said in the first place, albeit rudely.
The message “congratulations you found a bug” does not come from the app, it comes from the framework around the app. You managed to trick it into thinking that there’s a bug by editing a DOM element underneath the app while it wasn’t looking - something no user should be doing.
It’s a bit like pulling a spark plug off the distributor then complaining that the car doesn’t run properly.
I have no idea why you think that editing the list while the window is not in edit mode would be a good thing to do. Even if it might be a good thing - even if you’re a mechanic - when something goes wrong as a result it doesn’t make it a bug that we need to look into.
That’s why I pointed out that the problem was not with the app but with the person using it in the wrong way. It’s a shame that comes across as an insult - it’s really just pointing out that it appears you don’t know what you are doing. It came across from me as being testy and rude not because I’m defensive about bugs, but because I’m defensive about wasting time chasing user-induced red-herring bug reports.
It is unfortunate that I have been compelled to point this out “defensively”, but if you’re going to get all self-righteous after securing an apology in public then you too need to look at the video and look in the mirror.