#19253 closed enhancement (fixed)
History browser: highlight selected relation member row
| Reported by: | simon04 | Owned by: | simon04 |
|---|---|---|---|
| Priority: | normal | Milestone: | 20.05 |
| Component: | Core | Version: | |
| Keywords: | history browser table row | Cc: |
Description
Attachments (1)
Change History (7)
Changed 3 weeks ago by
| Attachment: | 2020-05-17-230025_1118x658_scrot.png added |
|---|
comment:1 Changed 3 weeks ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:2 follow-up: 3 Changed 3 weeks ago by
is it intended that the selected (= highlighted) row may contain different members?
Try v613 and v614.
comment:3 Changed 12 days ago by
Replying to GerdP:
is it intended that the selected (= highlighted) row may contain different members?
Try v613 and v614.
There seems to be a clinch if the order is reverted. Would be nice if in these situations instead of the complete row the same member would be highlighted in different rows.
comment:4 Changed 7 days ago by
I am not happy about the highlighting (selecting) if the member has a new position. In this case, please, highlight (select) the member on both sides. If it is not possible to select half a row, select both. Thanks
comment:5 follow-up: 6 Changed 6 days ago by
The behaviour is the same as in the way node diff (just highlighting the row, w/o any semantic check). Please open a separate ticket to change it. This is definitively out of scope the 20.05 milestone.
In 16458/josm: