Can that be part of the theme so could be individually tweaked if required ? (with improved defaults of course 
)
@TotallyInformation just to note, the tabs are a near-identical size to how they were in 4.1
When we allowed them to go smaller in previous releases, we got complaints they ended up hiding too much of the label so it has hard to distinguish them. Very much one of those items that will come down to personal preference and ultimately we have to pick a sensible default that displeases everyone equally.
Yes, anything can be tweaked with a custom theme. We just want to have the right defaults so users first thought isn't "I need to change that".
1 Like
Additionally, deploy requires closing everything first. In v4, the dark background made it clearer that a node was being edited, this is less obvious in v5.
v4 in edit
v4 not edit
v5 in edit
v5 not edit
Also, there seems to be a little bug in the editor, extra shade?
open edit
closed edit
That must be the browser. This is Edge in Windows.
I mean the open and closed states of a node, when you edit multiple nodes.
And I'm still talking about this shadow, in v5 when looking it's barely visible.
No problem, I get it. As long as they can easily be tweaked with CSS, we can adjust to taste. 
My eyesight problems over the last 6 months (and ongoing for at least 5 more) have made me keenly aware of what happens when a user has to change the default size/zoom of their computer screen.
[post removed, as not relevant to this beta - post about infinite canvas moved here instead]
1 Like
@hazymat the feature you're commenting on is not in this beta. Lets keep feedback on it to the issue you've already commented on.
Ok, pls ignore/delete. Thanks
The Flow Tabs do not look like that in Edge in Windows 11
I was just about to mention this when I remembered the previous post
Another minor quibble (sorry) the function editor pane no longer stretches to the bottom of the browser tab
I’ve found that old Dashboard 1 has some CSS that pushes those tabs up. Do you have the old dashboard installed ?
1 Like
You are quite right, I did have Dashboard 1 and once removed the Flow Tabs were as Nick showed.
Is it just me or am I missing the point of these floating/disconnected flow tabs from the actual flows. In terms of UX, the current flow label is 100% better than the floating labels (research has been done on this topic, would recommend Nielssen nn/group for reference). I really don't get this obsession, we also see it in browsers, and it is not an improvement IMO.
1 Like
the only thing that seemed really bad to me are the new tabs design. I dont like that gap. Instead of looking like a tab it seems like a button!
Another major issue is that it seems tabs can't go all the way to the left when the left side panel is closed. That NR logo and title must be gone when hidding the left side pannel. We can't have it appearing and disappearing. So, I think it is better to just remove the logo completely, or move the tabs back to be in the canvas region, one row below the header and deploy buttons.
take a look at vscode, when we hide the left side panel
2 Likes
One issue I see with the RH sidebar is the node reveal no longer works correctly.
With the RH panel open the debug node is not scrolled into view (it is already in view - just behind the panel)
With the panel closed, the scroll into view works.
At a guess, this new viewport (the area inside the scroll bars) is not used in the reveal calculation.
Related question. Folk (me included) have commented on how difficult it is to sometimes see the flashing orange border (esp colour blind) and I am curious if this is something on the table for the modernisation?
Ref: Better accessibility on search result highlighting - #31 by knolleary
2 Likes
@Steve-Mcl I've added issues for both of the items you raise to the plan.
Certainly the reveal function needs fixing. The search highlighting is in need of suggestions as to what would be better. Having scanned through the thread from two years ago that you've linked to, nothing jumped out at me (pun intended).
1 Like
It might help if the additional notification border were made wider? Perhaps 10 or 15px wider with a fade outwards (perhaps like a semi-transparent background surrounding the target node, slowly fading out completely). The flashing red border could be retained but the wider faded border could be made to fade out slower to give people more time to target it on the page.
This would make the target node a lot easier to find without being too disruptive.
Is there a reason why the search does not leave the target node selected? I have great difficulty seeing which is the target node after the search.
1 Like
What happened to the fade effect on tabs (flows) with long names?
