Elements still marked as changed even if changes were manually removed

[Dakon]

• download anything
• add a key
• manually remove that key (do NOT use "undo")
• click upload

The selected element is scheduled for upload, even if has the same state as before.

[stoecker]

JOSM does not track original state, so any changes are changes, also reverting changes. In the first menu you have "Update modified". This can be used to replace such "unchanged changes" with the original state.

[simon04]

I would like to keep this as a – complicated to implement – enhancement. This helps to avoid creating new versions for objects which in fact haven't changed. Often Undo is not applicable since dozens of other operations have been performed in the meantime.

[wiktorn]

On the other hand, I use this trick/bug sometimes, for example to refresh Nominatim indexing (when for some reason, it got the data wrong).

[stoecker]

It's not complicated to implement. You simply need to automatically do the "Update modified" before a new upload. But that needs additional time, may result in unexpected behaviour and I never considered that issue of a small number of unnecessary changes important enough to bother the users with the implications of that procedure.