Context Navigation

Changes between Initial Version and Version 1 of Ticket #18610, comment 7

initial	v1
17	17	The better JOSM gets in automatically handling critical situations and otherwise directly warning about it, the fewer this warning is needed.
18	18	How about showing a warning directly when an action is changing the relation in a critical way like `Incomplete <type> relation was modified. Valdidator needs all members to be downloaded in order to run test. Download (incomplete) members now ?´ and offer to download all (incomplete) members with option to remember answer for action, session and always like adding a duplicated member to a relation in relation editor.
19		Deleting a member and combining ways (normal mode) already show warnings but need an additional one, splitting ways is on the way and not critical, so we have problems when changing child nodes or roles of member ways and adding members ~~left~~ without any warning left as critical for multipolygon/boundary relations:
	19	Deleting a member and combining ways (normal mode) already show warnings but need an additional one, splitting ways is on the way and not critical, so we have problems when changing child nodes or roles of member ways and adding members without any warning left as critical for multipolygon/boundary relations:
20	20	* deleting end node
21	21	* unglue end node