@MadCcc@wctiger I would like to pick this up

I am unable to replicate the issue because the current behavior aligns with the overall expectations. When searching and selecting a node, the drop-down menu automatically closes. However, upon reopening the menu, the previous expansion state is retained. @MadCcc@wctiger

Hi @MadCcc I am not sure seeing the same behavior as you described in the sandbox link above - I agree that the dropdown closes as expected, but when I reopen it the expansion state is lost.

Here is what I am expecting:

And here is what I am currently seeing after search and selecting a node:

You should use controlled expandKeys to keep state.

You should use controlled expandKeys to keep state.

I believe you meant the props treeExpandedKeys ? I've tried to use that props to track the expansion state myself, but I wasn't able to figure out how to get that to work with the use case showed in the sandbox.

My confusion is, from reading the antd documentation I only see one event onTreeExpand can give expansion state but that event is only fired when clicking on the icon to expand/collapse node, it does not trigger when searching nor selecting a node. Do you mind point me to how would I get the expansion state when searching and selecting a node?

@wctiger Thank you for clarifying and helping to reproduce the issue. I attempted to track down the component and later realized that it is built off the rc-tree-select library. I have tagged @zombieJ, who is a maintainer of antd and rc-tree-select , to investigate this matter further.

I find a workaround for this issue.

Since the problem here is, when treeDefaultExpandedKeys is present, selecting a node via search lost the expansion state. So if I am managing the expansion state from outside when a node is selected, then it can be a valid workaround. The tricky thing is, I have to hand over the expansion state control back to the tree select when: 1 - a search is happening, 2 - user expands the tree. This is achieved by updating the treeExpandedKeys props:

state = {
      treeExpandedKeys: null
   };
  <TreeSelect
      showSearch
      value={value}
      treeDefaultExpandedKeys={defaultExpandedKeys}
      treeExpandedKeys={treeExpandedKeys}
      treeData={treeData}
      onChange={value => {
       // Make sure set the expandedKeys with the full path of the node here, not just the node value.
        const expandedKeysFromRoot = dfsFuncToFindKeysFromRoot(treeData, value);
        this.setState({ treeExpandedKeys: expandedKeysFromRoot });
      }}
      onSearch={() => {
        this.setState({ treeExpandedKeys: null });
      }}
      onTreeExpand={() => {
        this.setState({ treeExpandedKeys: null });
      }}
      // ... Other tree props
  />

@wctiger hi could you please explain more about "the full path of the node here" means?