URL
https://www.openstreetmap.org/edit#map=19/22.34097/114.13254
How to reproduce the issue?
- click on this node
- realize there is no Turn Restrictions Editor

Screenshot(s) or anything else?
This issue was found out because of another issue elsewhere: graphhopper/graphhopper#2907
Basically, I need the Turn Restrictions Editor to appear to describe the following valid paths:

Source A may only reach destination 1, and source B may only reach destination 2. No crossing paths allowed.
Clearly, the existing iD editor can handle turn restrictions via 1 way. What needs to be done here is very simple: make the Turn Restrictions Editor appear.
Someone else added the relevant turn restrictions to this area possibly via JOSM. Curiously, the iD editor knows about this added turn restriction, because it refuses to delete the node at source A saying how this would damage an OSM relation.
Which deployed environments do you see the issue in?
Released version at openstreetmap.org/edit
What version numbers does this issue effect?
2.27.3
Which browsers are you seeing this problem on?
Chrome
URL
https://www.openstreetmap.org/edit#map=19/22.34097/114.13254
How to reproduce the issue?
Screenshot(s) or anything else?
This issue was found out because of another issue elsewhere: graphhopper/graphhopper#2907
Basically, I need the Turn Restrictions Editor to appear to describe the following valid paths:
Source A may only reach destination 1, and source B may only reach destination 2. No crossing paths allowed.
Clearly, the existing iD editor can handle turn restrictions via 1 way. What needs to be done here is very simple: make the Turn Restrictions Editor appear.
Someone else added the relevant turn restrictions to this area possibly via JOSM. Curiously, the iD editor knows about this added turn restriction, because it refuses to delete the node at source A saying how this would damage an OSM relation.
Which deployed environments do you see the issue in?
Released version at openstreetmap.org/edit
What version numbers does this issue effect?
2.27.3
Which browsers are you seeing this problem on?
Chrome