This is a tricky example, exact steps are quite important:

Preparation:
Go to Root tag and create such structure of tags:

--- root
    --- JavaScript
        --- Class
        --- Function
    --- Programming

It is important to have `Programming` tag, because (what is interesting) without this tag there is no bug, because you need to be lower or on the same level in the tree as the level of the searched tag (probably).

I case steps (Network: no throttling)
1. expand all tree nodes
2. Search for "Java"

Result & expected result: loads search tree expanded so that "JavaScript" node is expanded.

II case steps (Network: no throttling)
1. collapse all elements in the tree
2. Search for "Java"

Result: tree is not expanded, and there is no visible "JavaScript" node even though we can see in the network panel (video) that this node was returned by the backend (and you cannot expand the tree nodes while searching)

Expected: loads search tree expanded so that "JavaScript" node is expanded.

III case steps (Network: Slow 3G)
1. collapse all elements in the tree
2. Search for "Jav"
3. Immediately after the request for the search for 2nd point was fired but not finished yet search for "Java" (by typing additional "a") causing the first request to be cancelled
Slow 3G allows you to perform 3rd point - without slowing the network, the response would be too fast to type another "a" letter at the end of "Jav", before first request is completed

Result & expected result: loads search tree expanded so that "JavaScript" node is expanded.

IV case steps (Network: Slow 3G)
1. collapse all elements in the tree
2. Search for "Java"

Result: tree is not expanded, and there is no visible "JavaScript" node.

Expected: loads search tree expanded so that "JavaScript" node is expanded.