Context Navigation

Changes between Version 2 and Version 17 of Ticket #24516

v2	v17
11	11	I think the same is true for tag values, e.g. the value for `direction_northwest:symbol` can be
12	12	`train_station;none;train_station`. Now, when I tag a differnt guidepost and enter the value for tag `direction_northwest:symbol` JOSM might suggest `train_station;none;train_station` instead of only `train_station` when I start typing "t" assuming that there is a tag `direction_northwest:symbol=train_station` in the data or in the presets.
	13
	14	Addition 1: Some tags like survey:date or check_date or start_date contain dates or years. It would be good if JOSM would sort those so that the oldest date comes last in the list of known values instead of sorting the values alphabetically (-> oldest date comes first). This is also a good idea for all tags with prefixes like check_date: and maybe also with suffixes like :date.
	15	Addition 2: The autocompletion text field for the upload comment should also use the most recent matching entry instead of the first in a list which seems to be sorted alphabetically. This is a problem when JOSM decides to empty the field because of preference `upload.comment.max-age` which is set to 14400 seconds (4 hours) by default.
	16	I've quite often not noticed this problem and uploaded with the wrong comment.