Hi There, I really enjoy the search functionality but one thing that irritates me is that I sometimes don't know which node is meant - since I can't remember which node I've already opened. What I would like is that nodes are highlighted (see blinking border) when I move the mouse over the search result: [node-highlight-search3] This screencast is particularly pertinent because all nodes are called "template" (the connected nodes make the context clear). To get this working, all I did was add these lines: div.on("mouseover", function(evt) { if ( node.z == RED.workspaces.active() ) { RED.view.reveal(node.id) } }); here. I explicitly don't change workspaces (to avoid confusion) by checking the 'z' property. Is there general interest in this?

[image] bakman2: no reason for the gray overlay I sense a circle starting up here - that was my point: the point of the overlay is that "don't modify the flow, I'm just searching it" - the grey overlay communicates that to the user. else it would be even more confusing. it's a communication element to the user: you are now searching this flow, you can't modify the flow while searching. fullstop. there isn't a search and modify feature in NR. And the click-out-and-disappear pattern is used for the editor and other panels, so this is a very Node-RED thing to be doing. Instead of a confirmation: "are you sure you want to exit the search?" dialog. now: don't come and say "well the editor panel doesn't have a grey overlay when it's open" - no it doesn't but the plugins that aren't usable when the editor is open do! I guess there is a case to be made for removing the grey overly for search if the flow does become interactive (i.e. node highlights).... I think I just went in a circle .... EDIT: i guess I was off-base: the edit panel also activates the grey overlay - so it is consistent behaviour. crazy how this never really occurred to me.

[image] gregorius: crazy how this never really occurred to me. Not really, this is how UI's should work! So intuitive that you don't notice. :smiley:

Sorry @gregorius but I am not understanding. div.on("mouseover", function(evt) { if ( node.z == RED.workspaces.active() ) { RED.view.reveal(node.id) } }); Is that in the actual node-red/packages/node_modules/@node-red/editor-client/src/js/ui /search.js code - as per the github stuff?

[image] Trying_to_learn: code - as per the github stuff? No it's[1] nowhere near the actually source code, it's basically what I did to get it working - locally. I'm using it over at Erlang-Red but can't - of course - use it inside Node-RED until someone inserts it there. For it to be inserted there, folks have to like it. For folks to like it, they have to post here in the forum saying "hey I like this, can we have this in Node-RED v5". For folks to post here, they need a keyboard ..... Anyone, this is an RFC - Request For Comment, including the code that is required to implement the feature. I'm not going to create a pull request because I don't know whether it would get merged or not. In the meantime, I'll continue on using Erlang-Red. EDIT: [1]= clarification "it" are the four five lines of code I posted - they aren't in the source code but could be inserted at the point that I link to.

@gregorius I can't think why we wouldn't chose to do this. A PR would be welcome - happy for this type of thing to slip into the master branch so would get picked up by any future 4.1.x maintenance release as well.

[image] knolleary: A PR would be welcome Reveal node in search results via mouseover master ← gorenje:patch-4 opened 12:04PM - 04 Dec 25 UTC (UTC) [image] gorenje +6 -0 ## Types of changes This highlights nodes in the search results using a mouse…over trigger. See forum https://discourse.nodered.org/t/highlight-nodes-in-search-results-list/99747 for a discussion. Put an `x` in the boxes that apply - [ ] Bugfix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) ## Proposed changes Highlight nodes in the search results using mouseover. Only those nodes in the current active workspace are revealed. Switching between workspaces would be too confusing - IMHO. ## Checklist - [x] I have read the [contribution guidelines](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md) - [x] For non-bugfix PRs, I have discussed this change on the forum/slack team. - [ ] I have run `npm run test` to verify the unit tests pass - [ ] I have added suitable unit tests to cover the new/changed functionality e'Voila! :slight_smile:

That would be kind of nice as I did mention this in my list of things wanted in the new release. [image] Suggestions for Node Red 5.0 Feature Requests I may need to put my thinking hat on and look more into that. Thanks.

Indeed it is there in the v5 beta. (though the orange highlight/flashing is hard to see due to the grey overlay - so will need some tweaking)

Just asking... How hard is it to change the colour? As a lot of nodes are orange in colour the contrast isn't that good. So if it was a better colour, it would be easier to see. (a lot of nodes: Said with tongue in cheek)

[image] dceejay: orange highlight/flashing is hard to see [image] Trying_to_learn: How hard is it to change the colour? I would not change a thing - my reasoning being that it is very hard to find something that works in all situations: A single node versus many hundreds, colour: function nodes (orange) or comment node (white). The current solution is the same as all other highlights, i.e. the blinking border is always used when highlighting nodes. Having two different highlights might be confusing. Perhaps the grey overlay could be less dark so that the blinking is easy to notice. But again might lead to confusion having two different overlays.

Highlight nodes in search results list

Core Development

Trying_to_learn 5 December 2025 20:58 17

That would be kind of nice as I did mention this in my list of things wanted in the new release.

Topic		Replies	Views
Search Flows results bug (I think) General	4	125	18 April 2025
Quickly sift through search results (node red palette) General	8	179	4 January 2025
Better accessibility on search result highlighting Feature Requests	32	702	2 April 2024
Feature request: Visual improvement of the search Feature Requests	11	326	27 January 2025
Highlight groups/nodes from description text using references Core Development feature-request-if-something-is-being-done	5	144	17 June 2025

Highlight nodes in search results list

Related topics