The `Slider` has been updated to match the Material 3 Design specifications.
Original behavior
The Material 3 Design specs for the `Slider` were updated in December 2023. To opt into the 2024 design spec, set the `Slider.year2023` flag to `false`. This is done to ensure that existing apps aren't affected by the updated design specifications.
New behavior
The `Slider` widget has a `year2023` flag that can be set to `false` to opt in to the updated design spec. The default value for the `year2023` flag is `true`, which means that the `Slider` uses the previous 2023 design specifications.
- Who is affected
- Applications and packages relying on the previous behaviour or signature. Code that uses Slider, Slider.year2023, SliderThemeData.year2023 and related APIs.
- Practical impact
- Behaviour or API differences that can break builds or change runtime behaviour.
- What action should I take?
- Follow the official migration guide below, update affected call sites, run `dart fix --apply` where a fix is available, then run your tests.
Official migration guide (excerpt, © The Flutter Authors, CC BY 3.0)
To opt into the updated design spec for the Slider,
set the year2023 flag to false:
Slider(
year2023: false,
value: _value,
onChanged: (value) {
setState(() {
_value = value;
});
},
),To update your entire app to use the updated Slider design, set the
SliderThemeData.year2023 property to false in your MaterialApp:
return MaterialApp(
theme: ThemeData(sliderTheme: const SliderThemeData(year2023: false)),
// ...
Slider(
value: _value,
onChanged: (value) {
setState(() {
_value = value;
});
},
),
// ...AI_PROVIDER (for example to openai-compatible with a local Ollama or LM Studio endpoint) to enable grounded explanations. Everything else on this page works without an AI provider.Listed in the official breaking-changes index (docs.flutter.dev/release/breaking-changes).
An official announcement or migration guide documents an intended behaviour or API change. A verified source change (git diff) shows code changed but does not by itself prove a public API is breaking. AI interpretations are labelled and never used to classify a change.
- Source commit
- b3045439b7c0
- Source last updated
- Oct 21, 2026
- Last synchronized
- Oct 21, 2026
- Publication status
- published
Publication history
- Oct 21, 2026, 8:31 PM: new → published (ingestion) — Backed by an official breaking-change/migration guide.
AI_PROVIDER (for example to openai-compatible with a local Ollama or LM Studio endpoint) to enable grounded explanations. Everything else on this page works without an AI provider.