The committers listed above are authorized under a signed CLA.

• ✅ login: piotrbogun / name: Piotr Bogun (957f701, f47cb1e)

Thanks for this. Given the change is being made to the common treelist component, we'll need to check other places that component is used to ensure it doesn't create undesirable behaviours elsewhere.

@knolleary I have done some testing and also found two issues. Can make new bug tickets for them. Please let me know your thoughts.

UI locations tested

These are the locations I was able to find where the component is used. I am most likely missing some spots.

• Right sidebar
  • Help tab
  • Info tab
• Top right kebab menu
  • Import/Export nodes dialog

Testing checks

• Navigating up/down with arrow keys
• Left/Right arrow keys expand/collapse sub trees.
• Enter/space key doesn't look to trigger expand/collapse and looks to be expected.
• Clicking on an item in the list will navigate you appropriately to the next previous item as expected.
  • One exception I noted here is with the welcome tours. They open a dialog and the treeList loses focus. I don't think in this situation we might want to re-focus the tree list item. But would appreciate your thoughts. Don't see any issue here from my change.

Bug found 1

When you filter on the TreeList, navigating with the arrow keys can lead you to focus on items that are not visible:

• Filter a tree list
• Expand a list item with children and focus it
• Navigating down will lead you to go through that subtree even though those elements are filtered out/hidden.
• If an info box exists, it will update correctly to the item you are currently on.

Bug found 2

When the treeList is big enough, you are able to navigate to an item that is overflowed out of scope.

EDIT: Ticket/PR here: #5421. Looks to be specifically widget based.

• Right kebab menu -> import nodes
• Select Examples
• Expand the tree until you have scrolling.
• Scroll to the middle, select and item.
• Navigating far up/down will lead you to items that you no longer see.

@piotrbogun thanks for investigating. Happy with the fix for bug 2 - have merged.

Please raise bug 1 as a separate issue. I'm working on the next maintenance release today - won't get the fix for that in, but it isn't critical.