Avoid adding new footway segment if crossing is connected to end of footway

[kallejre]

Description

Suppose the situation in the attached screenshot: we have a lone footway that is crossing a street. A crossing way is added where the crossing is, and after finishing, the popup suggests adding kerbs at both ends of the crossing. However, kerbs are not the only things added - two tiny unwanted footway segments are created on both ends of the crossing.

I understand that the current behaviour is reasonable when a crosswalk connects to the middle of an existing sidewalk (e.g. the northern end in the attached screenshot). However, when the crossing connects directly to the end of a single footway, Rapid should avoid creating redundant stub segments (as happened at the southern end).

Screenshots

Version

2.5.5

What browser are you seeing the problem on? What version are you running?

No response

The OS you're using

No response

Steps to reproduce

1. Add crossing way
2. Connect both ends of crossing to single footway (you now have three ways)
3. Let Rapid add curbs at ends of crossing
4. Crossing way is now shorter, and you have 5 sequentially connected ways

The browser URL at the time you encountered the bug

https://rapideditor.org/edit?way=1050503639#map=21.80/59.46036/24.67023&background=Maaamet-Estonia_Ortho&id=w-18,w-17

The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)

No response

[kallejre]

After mapping for a while, this issue has somewhat convenient workaround that after curbs and new footway segments are added, i can just move the curb node to other end of the tiny segment, essentially removing it and then adjust existing footway.

[bhousel]

Thanks for reporting @kallejre , yes from what I remember our intention was that the user could drag to adjust the curb nodes pretty easily if their suggested placement doesn’t match up.