Opened 13 years ago
Closed 13 years ago
#7245 closed defect (duplicate)
History window doesn't update both sides when an item is updated locally
Reported by: | rickmastfan67 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | history | Cc: |
Description
Steps to reproduce:
- Download any node, way, relation.
- Using a node as an example, just slighting move it to make a different version.
- Load up the "History" window.
Expected results:
The left side should agree with the right side.
What happens:
The left side of the History window just shows a duplicated entry of the last version in the OSM database, while the one on the right mentions that is was edited and the user is "anonymous" and has no changeset because the change hasn't been uploaded yet.
=====
I would expect that the left side would at least would put "anonymous" in the "User" column without a changeset number. In the "Date" column, I would expect nothing at all except maybe the current date/time of the users system. As for the "Version #", maybe a "-" to let people know that's the version that they have edited and it's not uploaded yet. As for the "CT" column, that should remain blank since JOSM doesn't always know if the user has agreed with the CT.
Attachments (1)
Change History (3)
comment:1 by , 13 years ago
Summary: | History window doesn't update both sides when an item is updated → History window doesn't update both sides when an item is updated locally |
---|
by , 13 years ago
Attachment: | history_doesnt_agree.png added |
---|
comment:2 by , 13 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Closed as duplicate of #7716.