Colin. I am very much aware you raise issues on core (and dashboard and...) (and I/we are VERY thankful ).
To clear up my post, good-first-issue is a common theme on GH where users seeking to get experienced in coding on open source hunt for issues tagged as "good-first-issue" - see here: good-first-issue · GitHub Topics · GitHub.
Typically these are small tasks perfect for beginners to make contributions.
The Label helps them find such issues. And with a sprinkle of luck, they land on this one and fix it
There could be a small 500ms delay or maybe a wait for "key up", or maybe the deletion would only trigger on "key up" (as opposed to "key down"). The key up thing is much better. Both actually are quite necessary. The delay should be represented by the highlight.
There is also Ctrl+Z, so accidents would not be that big a deal.
It seems I had completely misunderstood what is happening when an unused config node is deleted. It is not that the next unused node, that is under the mouse, is selected, it is just that when the mouse is hovered over a node it is highlighted and looks exactly the same as a selected node, but since it is not actually selected then hitting delete does nothing.
@jbudd please raise as a separate feature request topic, otherwise this topic becomes a mix of actual feedback on the beta and other new ideas that could be done any time.
@Colin similarly with the config nodes feedback - if you have thoughts on improving the UX of the config sidebar (I have many such thoughts...), please raise a dedicated topic.
).
