﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
23053	Confusing UX when modifying a relation	richlv	team	"==== What steps will reproduce the problem?
1. Download data that contains a relation with multiple members (reproduced with a route relation).
2. Select a relation member.
3. Doubleclick the relation entry in the tag panel to open the relation properties.
4. The selected way is highlighted in the ""Members"" section. Click the trashcan icon there to remove this member from the relation.
5. Observe the member tag panel still showing it as being part of the relation. Also right-clicking that entry and selecting the relation includes the removed member.

This is working as expected, as ""OK"" is not clicked in the relation properties.
Still, it confused me for a whole minute as a somewhat experienced JOSM user.
Making the relation properties window modal is not an option - but maybe there can be some visual indicator (a red bar with an exclamation mark icon might have helped me...) that would say (possibly upon mouseover) something like ""Changes in this window like adding or removing members won't affect other views until you click ""OK"".

A similar disconnect exists between an opened relation properties window and the main window - if we select a way and right-click a relation, and choose ""add selection to 1 relation"", this change is not reflected in the relation properties window.

This actually allows to create a conflict with myself - open relation dialog, add a way with the right-click method, remove a way in the dialog - clicking ""OK"" results in a conflict that's purely local.

Would it be reasonable to propagate all changes that happen outside the relation dialogs into them?

==== Please provide any additional information below. Attach a screenshot if possible.

{{{
URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2023-07-06 21:00:41 +0200 (Thu, 06 Jul 2023)
Build-Date:2023-07-07 01:30:58
Revision:18772
Relative:URL: ^/trunk

Identification: JOSM/1.5 (18772 en_GB) Mac OS X 10.15.7
OS Build number: Mac OS X 10.15.7 (19H2026)
Memory Usage: 2099 MB / 3641 MB (1302 MB allocated, but free)
Java version: 1.8.0_371-b11, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Look and Feel: com.apple.laf.AquaLookAndFeel
Screen: Display 1127230987 1920×1080 (scaling 1.00×1.00) Display 69733382 1680×1050 (scaling 1.00×1.00)
Maximum Screen Size: 1920×1080
Best cursor sizes: 16×16→16×16, 32×32→32×32
System property file.encoding: UTF-8
System property sun.jnu.encoding: UTF-8
Locale info: en_GB
Numbers with default locale: 1234567890 -> 1234567890
VM arguments: [-Djnlp.application.href=https://josm.openstreetmap.de/download/josm.jnlp, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlp.tk=awt, -Djnlpx.jvm=<java.home>/bin/java, -Djnlpx.splashport=-1, -Djnlpx.home=<java.home>/bin, -Djnlpx.remove=false, -Djnlpx.offline=false, -Djnlpx.relaunch=true, -Djnlpx.session.data=/var/folders/nl/flqxqsmj5q963r7tcnfrdt3c0000gn/T/session2291348669531784031, -Djnlpx.heapsize=NULL,NULL, -Djava.security.policy=file:<java.home>/lib/security/javaws.policy, -DtrustProxy=true, -Djnlpx.origFilenameArg=/Users/richlv/Library/Application Support/Oracle/Java/Deployment/cache/6.0/56/1ee8cfb8-72e8e992, -Dsun.awt.warmup=true, -Djava.security.manager]
Dataset consistency test: No problems found

Plugins:
+ HouseNumberTaggingTool (36097)
+ InfoMode (36079)
+ Mapillary (2.1.4)
+ PicLayer (1.0.2)
+ apache-commons (36034)
+ apache-http (35924)
+ buildings_tools (36097)
+ dataimport (36066)
+ ejml (35924)
+ geotools (36068)
+ imagery_offset_db (36079)
+ jackson (36034)
+ jaxb (35952)
+ jna (36005)
+ jts (36004)
+ measurement (36097)
+ opendata (36097)
+ pbf (36034)
+ photo_geotagging (36079)
+ reverter (36066)
+ undelete (36066)
+ utilsplugin2 (36097)

Map paint styles:
- https://josm.openstreetmap.de/josmfile?page=Styles/Coloured_Streets&zip=1

Last errors/warnings:
- 00031.544 W: java.net.SocketTimeoutException: connect timed out
- 00031.544 E: java.net.SocketTimeoutException: connect timed out
- 00031.545 E: org.openstreetmap.josm.io.OsmTransferException: Could not connect to the OSM server. Please check your internet connection.. Cause: java.net.SocketTimeoutException: connect timed out
- 00064.961 W: java.net.SocketTimeoutException: connect timed out
- 00070.029 W: Already here java.net.SocketTimeoutException: connect timed out
- 00070.029 E: java.net.SocketTimeoutException: connect timed out
- 00070.031 W: org.openstreetmap.josm.io.OsmTransferException: Could not connect to the OSM server. Please check your internet connection.. Cause: java.net.SocketTimeoutException: connect timed out
}}}
"	enhancement	new	normal		Core	tested		template_report	
