I have a template node at the top of a dashboard tab, under it is a table node.
When you click on a table row, the contents of that selected row pop up in the template.
The problem is that the table node can often extend beyond the bottom of the screen height.
When you scroll down, the template node scrolls off the top of screen and so you are constantly scrolling down, clicking blindly, scrolling up to read the details, then scrolling back down to try and find where you were and clicking and scrolling madness ensures.
Since a picture is worth a 1000 words, here is how the screen looks when you first start....
Can I highlight the row I clicked on?
Its too easy to forget what row you last selected when you are scrolling up and down.
Can I have the table scroll UNDER the template node at the top?
I have seen websites do this where their header / menu is always at the top of screen even as you scroll down. Very powerful and clean.
(Note, having the table scroll under the template would pretty much eliminate the need for the row highlight I suspect).
How have you set the height of the table ? If you set it so its less than the page height the table contents should scroll inside their widget and not the whole page.
Again, good idea, been a while since I have looked....
Just imported all the examples into a fresh Node-RED build and none of the example tables highlighted the row....
Will keep kicking at it, thanks for the weekend support.
The feature is called „select“ row! And it is included in the last example. Here is the doc:
Think setting “selectable“:1 should highlight only the last selected row.
@dceejay I mentioned it a while ago that there is no limit for the widget hight if set to auto in ui-table hight always = amount of rows. Do you think a limit is usefull? I never use auto so I don‘t care
msg.ui_control.tabulator[selectable]=1;
is throwing; "TypeError: Cannot read property 'tabulator' of undefined"
So yeah, its very confusing for a low-code guy like me.... will keep chipping at it, hopefully will get something we can post here for others.
"change tab or ..." is the right option, You can see the output in the demo flow (on the dashboard and with the debug nodes. Every row click send a standard message. if you need other function you have to write your own callback function
For those following along or finding this via a search.. After more than a few hours work I have had to give up and move on.
The ui control node just does not output anything (ever), so thus I cant detect a table row selection.
Such is life.
Thanks everyone for you help.
Making the table shorter makes a big usability improvement to the system.
eh ? that doesn't compute - the ui_control node will provide a change event every time the dashboard connects or changes tab (or every deploy)... the ui_table node provides events when you click on a row.
What is being suggested is to use the ui_control change event to provide an input to the table to tell it to be selectable. - You also then need to catch any select event from the table and save it so that it know which row was selected, so you can then feed that back in on next change, etc.
I have been using Node-RED for over 5 years and have a bizillian hours into this project and honestly, this is the first time it just flat out has not worked... no errors, and no debug messages. It just simply does not do anything.
You can click that row all you like and nothing will ever get detected.
The only time you get a debug message is when you change tabs in the dashboard.
At first I thought it was because I was using the wrong ui table node.
I had node-red-ui-node-table nodes installed. So I exported everything, uninstalled that node and installed
node-red-node-ui-table and reimported all my tables (that took about an hour).
Here is the table node I am now using.
hight always = amount of rows. Do you think a limit is usefull? I never use auto so I don‘t care 
