Merge branch 'next' into renovate/mui-core

Signed-off-by: Alexandre Fauquette <[email protected]>

.github/workflows/no-response.yml

@@ -8,8 +8,10 @@ on:
   issue_comment:
     types: [created]
   schedule:
-    # Schedule for five minutes after the hour, every hour
-    - cron: '5 * * * *'
+    # These runs in our repos are spread evenly throughout the day to avoid hitting rate limits.
+    # If you change this schedule, consider changing the remaining repositories as well.
+    # Runs at 3 am, 3 pm
+    - cron: '0 3,15 * * *'
 
 permissions: {}
 

docs/data/migration/migration-tree-view-v6/migration-tree-view-v6.md

@@ -402,6 +402,38 @@ you can use the new `onItemSelectionToggle` prop which is called whenever an ite
 
 :::
 
+### Focus the Tree Item instead of the Tree View
+
+The focus is now applied to the Tree Item root element instead of the Tree View root element.
+
+This change will allow new features that require the focus to be on the Tree Item,
+like the drag and drop reordering of items.
+It also solves several issues with focus management,
+like the inability to scroll to the focused item when a lot of items are rendered.
+
+This will mostly impact how you write tests to interact with the Tree View:
+
+For example, if you were writing a test with `react-testing-library`, here is what the changes could look like:
+
+```diff
+ it('test example on first item', () => {
+   const { getByRole } = render(
+     <SimpleTreeView>
+       <TreeItem itemId="one">One</TreeItem>
+       <TreeItem itemId="two">Two</TreeItem>
+    </SimpleTreeView>
+   );
+-  const tree = getByRole('tree');
++  const treeItem = getByRole('treeitem', { name: 'One' });
+   act(() => {
+-    tree.focus();
++    treeItem.focus();
+   });
+-  fireEvent.keyDown(tree, { key: 'ArrowDown' });
++  fireEvent.keyDown(treeItem, { key: 'ArrowDown' });
+ })
+```
+
 ### ✅ Use `useTreeItemState` instead of `useTreeItem`
 
 The `useTreeItem` hook has been renamed `useTreeItemState`.