id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
22355	"Some ideas to improve Tags/Membership window and ""add tag""/""change tag"" dialogue"	anonymous	team	"**Some ideas to improve:**

I)  ""add tag"" (""change tag"" etc.) dialogue
II)  Tags/Membership window

-------------------------------------------------
**I) ""add tag"" (""change tag"" etc.) dialogue**
-------------------------------------------------

''I.a) KEYS''

A check of the used keys already during the input would avoid incorrectly written keys early. 

Example 1: capital / lowercase letters in keys (e.g. 'node' versus 'Node') 

Example 2: wrong spelling of the key (e.g. 'railway:switch:electric' versus '... :eleektrik' ):

I think a simple display is sufficient: I could imagine that the background appears red (analogous to the 'Search' dialog, in case of an incorrect search string). In addition, a button with the inscription 'correct' could be displayed. Pressing the button takes over the correct written key. Alternatively, a double-click in the input-field could do this. If an automatic correction is not possible, the button remains inactive (gray). If necessary/prossible, keys are suggested by a (filtered) drop-down menu. (This menu is already available as standard without filtering.) 


''I.b) VALUES''

The same could be helpful for values.


-------------------------------------------------
**II)  Tags/Membership window**
-------------------------------------------------

''II.a  Wrong writen and unknown keys/values''

As described above - wrong writen keys/values should be explicitly indicated (by a red background) also in the list of keys/values in the Tags/Membership window. The reason is, these could be / have been taken over incorrectly Key/Values by (copy/)paste. Also it is possible to detect and correct now a day/today wrong keys/values from history. 

''II.b  Changed values''

Values that have been changed should be displayed differently (e.g. blue color of the font / blue color of the background). If the computer screen offers sufficient space, the display of the previous value in a second line (in gray font) would be desirable. Alternatively, a display of the old value on mouse-over or in the context menu (right click) or in a three-column display (this depends on the screen size (mostly I use a 4K screen for JOSM)). 

I feel - after changing the selection between (one) nodes/ways, a simple indication via image (for ""new""/""change"") should be sufficient at first also.

Regards
mikeho"	enhancement	new	normal		Core			improve Tags/Membership window	mikeho