You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report @mxxcon - It looks like the crossing-tag-sync code was running in some situations when it shouldn't.
If the user removes the crossing tags from the junction node, yes we want to sync that removal to the parent way - but if the user is just touching the kerb which has no crossing tags, we shouldn't try push "no crossing tags" up to the way.
I fixed things so that it will only try a sync if a crossing tag was actually involved in what the user did.
I just published a v2.2.1 patch release on rapideditor.org that includes this fix.
Description
Curb node 11418980879 is connected to crosswalk way 1231253214 which has tags:
and it looks like this
If I modify any property of that curb, the mentioned crosswalk suddenly loses
crossing=traffic_signals
tagAnd it looks like
This problems exist on 2.2 and this canary build too.
Screenshots
No response
Version
2.2.0
What browser are you seeing the problem on? What version are you running?
Chrome v121.0
The OS you're using
win
Steps to reproduce
The browser URL at the time you encountered the bug
https://rapideditor.org/canary#background=EsriWorldImagery&datasets=fbRoads,msBuildings&disable_features=boundaries&id=n11418980879&map=20.92/40.59189/-73.93729
The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36
The text was updated successfully, but these errors were encountered: