Make an item with children. Collapse the item. Add a new item underneath it (at the same height). Using tab (or other shortcut/command) move the item underneath the collapsed item above.
Expected result
The collapsed item stays collapsed, and the item below just moves into the parent item. This is the behavior if you were to manually drag and then hold below and to the right of the parent item, placing it underneath the parent item (i.e. thereās UX precedence for this behavior).
Actual result
The item is moved under the parent, but the parent item now becomes uncollapsed.
Environment
Chrome, ChromeOS. Probably all platforms but havenāt had the time to test.
It seems thereās a UX mismatch between when you drag an item underneath another (holding to the right under it) and when you ātabā it under. To me it seems like they should behave the same, is there a reason they are different in respect to a collapsed parent item?
My argument would be dragging an item under a parent is more deliberate. Itās more unlikely to be an accident than hitting Tab.
Also, when youāre Tabbing, your focus is on there; we want to preserve it so you can continue typing. Compare this to drag nā drop, where the focus is already lost and you wouldnāt expect to continue editing.