Can't use editing keyboard shortcuts on tagless nodes with v2.2

[mxxcon]

Description

I'm not sure if it's a bug or a feature, but keyboard shortcuts are not working because windows focus automatically gets locked to the search box.
For example if I draw a line, add a node to it, i can't use X shortcut to split it

Screenshots

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

1. Draw a sidewalk
2. Add a node to it
3. Try to use X shortcut it split it

The browser URL at the time you encountered the bug

https://rapideditor.org/edit?#background=EsriWorldImagery&datasets=fbRoads,msBuildings&disable_features=buildings,boundaries&gpx=https://mwai-tasking-manager-production-api.mapwith.ai/api/v2/projects/149/tasks/queries/gpx/%3Ftasks%3D375&map=20.97/40.59033/-73.92740

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

[mxxcon]

Also can't delete a tagless node or disconnect 2 ways on the intersection of a tagless node with D

[Bonkles]

Okay, I have run a git bisect for all 120+ commits since tag 2.1 and found the commit where this got introduced.

It was commit c308af25e705ac226d6ce6e85fbbd400c66cdd9e, where we made a fix for the walkthrough in #1236.

Now investigating root cause.

[Bonkles]

In addition to hogging the focus, it looks like the search input isn't being cleared between selections. This is likely related. Normally when you pick a preset the search input is cleared, but it appears this is not the case either:

bug_1265.mov

[bos]

Is this fix live?

[bhousel]

Is this fix live?

I believe you can try it in https://rapideditor.org/canary right now..
I'll push a patch to the main Rapid site soon that includes fixes for this and the other issue @mxxcon found.

[bhousel]

Thanks for the report @mxxcon & @bos , and shout out to @Bonkles for the quick fix.
I just published a v2.2.1 patch release to rapideditor.org that includes this fix.