☂️ Rework `Slider` & `RangeSlider` widgets

[rydmike]

☂️ Umbrella of Slider and RangeSlider issues

Rework the Slider & RangeSlider widgets to address most if not all issues listed below.

---

Slider

Callback issues

• RangeSlider onChangeEnd method called twice when used in a showModalBottomSheet #128433
• Slider onChangeEnd is never called when arrow keys are used. #123315
• Sliders can be changed accidentally by swiping up/down to scroll the page #120596
• Slider::onChanged fires twice after window is resized horizontally. #112290
• Slider skip some onChange on divisions when fast movement #74312
• Sliders Number Problem #66341
• Slider label clips the screen #63293

Value indicator

• Slider label never goes away when clicking slider to new value #123313
• Slider label shape has poor looks with transparency #122793
• Slider does not show value indicator when focused. #113538
• Flutter Slider Label showing strange numbers #73787
• Discrete Slider/RangeSlider has interpolation (?) errors #39510

Thumb

• [Proposal] Allow default Slider thumb shape to be easily customizable  #113781
• [Slider] Thumb's center doesn't align with division's center #62567

Performance

• Slider relies on brittle paint order to work properly #98770
• Slider has a slight a lag when drag #51715

Slider error issues

• Slider in Draggable.feedback does not work as expected and throws an error LeaderLayer anchor must come before FollowerLayer in paint order, but the reverse was true.  #97292

New feature and Proposals

• Support for range value to be from anywhere in the Slider widget, separate from min/max value #63330
• [Material] Update hover + focused + pressed states for mouse on Slider and Range Slider #62214
• Flutter slider should have the feature to show value indicator all the time, not just while gesturing #34704
• Touch up/down status for slider.dart #32768

Accessibility

• Slider and RangeSlider thumb accessibility issues #114225

Documentation

• Slider.label documentation should be clearer about behavior with continuous sliders #74098

Tests

• [web][tests] Re-enable Slider tests #34251

RangeSlider

Value indicator

• RangeSlider labels for value change overlaps #76466

New features and Proposals

• Current values are missing from RangeSliderThumbShape paint() method #62486
• [Material] Add focus state, highlight state, and keyboard shortcuts to RangeSlider #53958
• [Material] Create a MaterialTapTargetSize for slider and consume in Range Slider #33795
• RangeSlider should have an option to include a current value indicator #126746

Functionality

• A discrete RangeSlider is not draggable inside a ListView. #51620
• [RangeSlider] [Flutter 3.10] LateInitializationError: Field '_startThumbCenter@280317193' has not been initialized. #126648

Accessibility

• [Android Web] TalkBack does not read out value changes on increase/decrease. Ex: RangeSlider #32229

Slider Updates Project

Slider Updates (view)

[TahaTesser]

A simple umbrella issue is effective and feels helpful in this case, since there are a large number of open issues related to sliders.

Agree! Thank you for creating this.

Edit:

I've removed the CupertinoSlider as it is not part of material and is very different in scope as well.

[rydmike]

Sure and agreed @TahaTesser. There were not so many of them anyway. While collectiong the list, I did notice that some of the issues did seem to have some overlap between Slider/RangeSlider and CupertinoSlider as well, but not many.

By the way, the CupertinoSlider has one of the features requested for Slider (#113370) out of the box. It actually only has the mode where you always have to slide the thumb, you can not click on the track to move the thumb. In some use cases I stoped using platform adaptive Slider.adaptive, as I did not like that for the use cases in question, even on iOS. I do agree with the feature request though, for some use cases it can be the other way around, that it is a requirement to have that behavior, then currently Slider is not a suitable.

---

Edit:
Confirmed the CupertinoSlider behavior, previous entry said it was just based on memory and that I was not 100% sure it behaved that way. Now verified this by testing it in repos where I still use Slider.adaptive.

[stuartmorgan-g]

A simple umbrella issue is effective and feels helpful in this case, since there are a large number of open issues related to sliders.

This seems like it should be a label or project.

Our guidelines for issues are that they must be actionable, which means we should be able to describe the conditions under which the issue would be closed. What is that condition here?

[TahaTesser]

A simple umbrella issue is effective and feels helpful in this case, since there are a large number of open issues related to sliders.

This seems like it should be a label or project.

Our guidelines for issues are that they must be actionable, which means we should be able to describe the conditions under which the issue would be closed. What is that condition here?

I'm doing a major rework on these two widgets under Slider Updates (view).
Perhaps a better title would be needed?

[stuartmorgan-g]

So the goal of the project is to fix every issue on this list? It's a much longer list than the project you linked to currently has.

It would help if the issue were updated to explain what the end state is; right now the text sounds like it's describing a list of every issue in a category rather than a work list for a bounded project.

[TahaTesser]

So the goal of the project is to fix every issue on this list? It's a much longer list than the project you linked to currently has.

It would help if the issue were updated to explain what the end state is; right now the text sounds like it's describing a list of every issue in a category rather than a work list for a bounded project.

Updated description to cover areas of the widgets to be fixed and removed some out of scope engine related issues.