Deleting a way with new nodes produces invalid osm file

[balrogg@…]

If you add a new node to an existing way, then change your mind and delete the way and save the file, the way will be saved with action='delete' and will contain the new node's id (such as -25). The node, however will not be in the file because new nodes, when deleted, are forgotten. On loading the file into JOSM again, JOSM will say that it had to skip the way because it contained a non-existent node. Logically the deletion of the way will not be in the changeset when uploading to OSM.

I think the easiest fix would be to ignore missing nodes when loading deleted ways. A different fix would be to remove new nodes from ways the moment they are deleted.

[stoecker]

Last solution seems right. When deleting ways/relations the new nodes/elements should be stripped first.

[Gubaer]

fixed in r1656