mui · oliviertassinari · Aug 6, 2025 · Aug 6, 2025 · oliviertassinari · Aug 6, 2025
diff --git a/CHANGELOG.old.md b/CHANGELOG.old.md
diff --git a/docs/data/material/components/app-bar/app-bar.md b/docs/data/material/components/app-bar/app-bar.md
@@ -123,7 +123,6 @@ A floating action button appears on scroll to make it easy to get back to the to
 #### Arguments
 
 1. `options` (_object_ [optional]):
-
    - `options.disableHysteresis` (_bool_ [optional]): Defaults to `false`. Disable the hysteresis. Ignore the scroll direction when determining the `trigger` value.
    - `options.target` (_Node_ [optional]): Defaults to `window`.
    - `options.threshold` (_number_ [optional]): Defaults to `100`. Change the `trigger` value when the vertical scroll strictly crosses this threshold (exclusive).

diff --git a/docs/data/material/guides/api/api.md b/docs/data/material/guides/api/api.md
@@ -89,7 +89,6 @@ Nested components inside a component have:
 ### Prop naming
 
 - **Boolean**
-
   - The default value of a boolean prop should be `false`. This allows for better shorthand notation. Consider an example of an input that is enabled by default. How should you name the prop that controls this state? It should be called `disabled`:
 
     ```jsx

diff --git a/docs/data/material/integrations/interoperability/interoperability.md b/docs/data/material/integrations/interoperability/interoperability.md
@@ -634,7 +634,6 @@ If you use a different framework, or already have set up your project, follow th
 ```
 
 3. Add the `important` option, using the id of your app wrapper.
-
    - For Next.js projects, use `#__next`. **Note for Next.js 13+ Users (App Router)**: You must now manually add `id="__next"` to your root element (typically `<body>`), as Next.js no longer adds it automatically:
 
    ```tsx

diff --git a/docs/data/material/integrations/tailwindcss/tailwindcss-v4.md b/docs/data/material/integrations/tailwindcss/tailwindcss-v4.md
@@ -417,18 +417,18 @@ If you want to use Material UI theme tokens in your Tailwind CSS classes, copy
 
 /* Material UI typography utilities */
 @utility typography-* {
-  font: --value(--font- *);
+  font: --value(--font-*);
 }
 
 /* Material UI overlay utilities */
 @utility overlay-* {
-  background-image: --value(--overlay- *);
+  background-image: --value(--overlay-*);
 }
 
 /* Material UI elevation utilities */
 @utility elevation-* {
-  background-image: --value(--overlay- *);
-  box-shadow: --value(--shadow- *);
+  background-image: --value(--overlay-*);
+  box-shadow: --value(--shadow-*);
 }
 ```
 

diff --git a/docs/data/material/migration/migration-v3/migration-v3.md b/docs/data/material/migration/migration-v3/migration-v3.md
@@ -269,7 +269,6 @@ This change is explained in more detail in the [TypeScript guide](/material-ui/g
 ### List
 
 - [List] Rework the list components to match the specification:
-
   - The `ListItemAvatar` component is required when using an avatar.
   - The `ListItemIcon` component is required when using a left checkbox.
   - The `edge` property should be set on the icon buttons.
@@ -342,7 +341,6 @@ This change is explained in more detail in the [TypeScript guide](/material-ui/g
 ### Snackbar
 
 - [Snackbar] Match the new specification.
-
   - Change the dimensions
   - Change the default transition from `Slide` to `Grow`.
 
@@ -470,7 +468,6 @@ This change is explained in more detail in the [TypeScript guide](/material-ui/g
   ```
 
   It's consistent with other React projects:
-
   - material-ui => MaterialUI
   - react-dom => ReactDOM
   - prop-types => PropTypes
diff --git a/docs/data/system/styled/styled.md b/docs/data/system/styled/styled.md
@@ -36,7 +36,6 @@ It aims to solve the same problem, but also provides the following benefits:
 
 1. `Component`: The component that will be wrapped.
 2. `options` (_object_ [optional]):
-
    - `options.shouldForwardProp` (_`(prop: string) => bool`_ [optional]): Indicates whether the `prop` should be forwarded to the `Component`.
    - `options.label` (_string_ [optional]): The suffix of the style sheet. Useful for debugging.
    - `options.name` (_string_ [optional]): The key used under `theme.components` for specifying `styleOverrides` and `variants`. Also used for generating the `label`.

diff --git a/docs/pages/blog/2019-developer-survey-results.md b/docs/pages/blog/2019-developer-survey-results.md
@@ -59,7 +59,6 @@ The prefix corresponds to the number of times the concern was mentioned.
 It's sorted descending, with the most important concerns first:
 
 - 135 **More components:**
-
   - 56 Non-specific
   - 21 Date picker
   - 10 Autocomplete
@@ -85,15 +84,13 @@ It's sorted descending, with the most important concerns first:
   - 1 Transfer
 
 - 50 **Better customization:**
-
   - 23 Non-specific
   - 15 Docs
   - 8 Easier
   - 3 Theme
   - 1 Colors
 
 - 36 **Better documentation:**
-
   - 11 Non-specific
   - 7 More examples
   - 5 Beginner tutorials
@@ -107,28 +104,24 @@ It's sorted descending, with the most important concerns first:
   - 1 Server-side rendering
 
 - 31 **TypeScript:**
-
   - 14 Non-specific
   - 13 Migrate more demos
   - 3 withStyles -> makeStyles
   - 1 Rewrite
 
 - 24 **Performance:**
-
   - 23 Non-specific
   - 1 Table
 
 - 19 **Bundle size**
 - 17 **Material Design Update**
 - 16 **styled-components:**
-
   - 10 Support
   - 6 Migration
 
 - 14 **Fewer breaking changes**
 - 10 **More page layout examples**
 - 9 **Theme:**
-
   - 3 More colors
   - 3 Live editor
   - 1 Non-material font example
@@ -137,7 +130,6 @@ It's sorted descending, with the most important concerns first:
 - 8 **React.StrictMode support**
 - 8 **React Native support**
 - 6 **Accessibility:**
-
   - 4 Non specific
   - 1 Docs
   - 1 SkipNav

diff --git a/docs/pages/blog/2020-q1-update.md b/docs/pages/blog/2020-q1-update.md
@@ -46,15 +46,12 @@ Here are the most significant improvements since the beginning of the year:
   </video>
 
 - ⚛️ We have worked on improving developer experience inside text editors.
-
   - We have migrated prop descriptions from JSDoc to TypeScript for 60% of the components. Back-and-forths with the documentation API will be less frequent:
 
   ![props](/static/blog/2020-q1-update/props.png)
-
   - The color modules come with new previews:
 
   ![colors](/static/blog/2020-q1-update/colors.png)
-
   - We have collaborated with [Andy Edwards](https://github.com/jedwards1211) to provide [snippets](https://marketplace.visualstudio.com/items?itemName=vscodeshift.material-ui-snippets) with Visual Studio Code:
 
   ![snippets](/static/blog/2020-q1-update/snippets.gif)
@@ -98,7 +95,6 @@ We'll do our best, no guarantee!
 
 - 🔥 We will start to work on the [next major: v5](https://github.com/mui/material-ui/issues/20012).
   You can expect the following:
-
   - A feature freeze on v4.
   - The introduction of deprecation messages in the next v4 minors. These messages will help developers upgrade to v5.
   - A progressive bug fixes freeze on v4, with the exception of security issues and important bugs.

diff --git a/docs/pages/blog/2020-q2-update.md b/docs/pages/blog/2020-q2-update.md
@@ -65,7 +65,6 @@ Here are the most significant improvements since March 2020:
 ```
 
 - 📆 On the [date picker](https://mui.com/x/react-date-pickers/):
-
   - A new `renderInput` API which matches that of the autocomplete component has been added.
   - The input mask UX has been improved.
   - Support for `value={null}` has been added.
@@ -102,7 +101,6 @@ We'll do our best, no guarantee!
 These are objectives, no guarantees:
 
 - 🏢 We will [hire](/careers/) 3 full-time roles in the team.
-
   - One person on the open-source side to focus on the design system problem (unstyled, theming, styling, etc.): ✅ starting in two months.
   - One person on the enterprise side to consolidate the development of the advanced components: 🚧 Work in progress.
   - One person on a role yet to defined: 🚧 Work in progress.

diff --git a/docs/pages/blog/2021-q1-update.md b/docs/pages/blog/2021-q1-update.md
@@ -87,7 +87,6 @@ This new feature removes the need to create a wrapper component.
 - 🦴 We have migrated a couple of components to the `@mui/base` package.
   The aim of the package is to host the unstyled and headless (hooks) components.
   So far, you can only find:
-
   - Backdrop
   - Badge
   - Focus trap

diff --git a/docs/pages/blog/2021-q2-update.md b/docs/pages/blog/2021-q2-update.md
@@ -26,7 +26,6 @@ Here are the most significant improvements since March 2021.
 ### Core components
 
 - 🔥 We've made enough progress to ship [v5.0.0-beta.0](https://github.com/mui/material-ui/releases/tag/v5.0.0-beta.0). Here are a few statistics to give an idea of the effort that went into it:
-
   - [12 months](/blog/2020-q2-update/#product) of dedicated focus.
     We stopped work on v4 early on to fully dedicate to v5.
   - 3,475 pull requests.

diff --git a/docs/pages/blog/2021-q3-update.md b/docs/pages/blog/2021-q3-update.md
@@ -31,7 +31,6 @@ Here are the most significant improvements since early July 2021.
   You can read more about it in the [release blog post](/blog/mui-core-v5/).
 - ✨ We also introduced a brand new [product page](/core/) this quarter to better present what the Core is about.
 - 🔎 We've reworked the search experience in the docs:
-
   - The component pages now rank before the API pages.
   - Instead of only displaying up to 5 results, you can scroll for more results.
   - An icon illustrates the nature of the match; either a page, a header, or a paragraph.
@@ -51,7 +50,6 @@ Here are the most significant improvements since early July 2021.
 
 - We introduced a new [package of components without styles](https://www.npmjs.com/package/@mui/base), laying the foundations for supporting multiple design systems with headless components.
   While it was tough to balance the time between working on v5 stable and developing the unstyled components, we still managed to introduce the first few:
-
   - [Autocomplete](/material-ui/react-autocomplete/#useautocomplete)
 
   ```jsx

diff --git a/docs/pages/blog/2021.md b/docs/pages/blog/2021.md
@@ -74,7 +74,6 @@ We have achieved most of what we could have hoped for.
 - We have broken down the demos into smaller and focus on one aspect at a time.
 - We have polished and promoted most of the components that were in the lab to `@mui/material`.
 - We have introduced many new components:
-
   - [Masonry](/material-ui/react-masonry/)
   - [Stack](/material-ui/react-stack/)
   - [Trap Focus](https://v6.mui.com/base-ui/react-focus-trap/)

diff --git a/docs/pages/blog/mui-core-v5.md b/docs/pages/blog/mui-core-v5.md
@@ -120,7 +120,6 @@ After [exploring](https://github.com/mui/material-ui/issues/22342) many differen
 1. We have made `styled()` the lowest level primitive to add styles.
    This API is already known by many.
 2. We have defined a common interface with concrete implementations:
-
    - `@mui/styled-engine`: implemented with Emotion (default).
    - `@mui/styled-engine-sc`: implemented with styled-components
    - If you are using a different styling library, feel free to contribute a wrapper. For instance, there is [one attempt with goober](https://github.com/mui/material-ui/pull/27776), a library obsessing on bundle size (3kB gzipped).

diff --git a/docs/pages/blog/mui-x-v6-alpha-zero.md b/docs/pages/blog/mui-x-v6-alpha-zero.md
@@ -63,14 +63,12 @@ It contains the highlights that will be included in the first versions.
 
 - **Extended customization abilities**.\
   We want to empower more users to employ the Data Grid for complex use cases.
-
   - [ApiRef in the community package](https://github.com/mui/mui-x/issues/6147).
   - [Filtering on header](https://github.com/mui/mui-x/issues/6247).
   - [Use the Data Grid internal components outside the grid](https://github.com/mui/mui-x/issues/2522).
 
 - **Improved look & feel**\
   We're polishing edges in terms of design and usability.
-
   - [New column menu](https://github.com/mui/mui-x/issues/4929).
   - [New column visibility panel](https://github.com/mui/mui-x/issues/5700).
   - [Column resize bar only on hover](https://github.com/mui/mui-x/issues/1623).
@@ -83,7 +81,6 @@ It contains the highlights that will be included in the first versions.
 - **Improved UX**\
   In the previous version we focused on developer experience and overall stability of the components.
   Now we're tackling ways to improve usability.
-
   - [Remove the clock view on time pickers (for desktop)](https://github.com/mui/mui-x/issues/4483).
   - [Visually edit a range by dragging date markers](https://github.com/mui/mui-x/issues/5311).
   - [Range shortcuts](https://github.com/mui/mui-x/issues/4563).

diff --git a/docs/pages/blog/premium-plan-release.md b/docs/pages/blog/premium-plan-release.md
@@ -87,7 +87,6 @@ Their last renewal can have a support duration of up to 5 years.
 - **Cost per developer seat**
 
   We're lowering our base price points, particularly for Pro users. Fees are billed annually.
-
   - Pro: $249 → $180/year or $15/month
   - Premium: $599 → $588/year or $49/month **($444/year - early bird)**
 

diff --git a/docs/pages/blog/v6-beta-pickers.md b/docs/pages/blog/v6-beta-pickers.md
@@ -111,7 +111,6 @@ Now that you've seen what's fundamentally changed with the Pickers, let's briefl
 - **Default render input**\
   You don't need to provide the usual `TextField` on `renderInput` anymore unless you need it customized.
   In which case you can do it by:
-
   1. Customizing through props via `field` and `input` slots ([codebox example](https://codesandbox.io/p/sandbox/customizing-fields-with-props-o66r1c?file=/demo.tsx)).
   2. Build a new field component using the Field's headless API (documentation coming soon).
   3. Use an entirely [custom text field](https://next.mui.com/x/react-date-pickers/date-picker/#custom-input-component) to suit your use case.
-Original file line number
+Diff line change
@@ Expand Up / @@ -89,7 +89,6 @@ Nested components inside a component have: @@
     ### Prop naming
     - **Boolean**
       - The default value of a boolean prop should be `false`. This allows for better shorthand notation. Consider an example of an input that is enabled by default. How should you name the prop that controls this state? It should be called `disabled`:
         ```jsx
@@ Expand Down @@