MudDateRangePicker ResetAsync() does not affect the DateRange or the current focused period

[kellyrmartin]

Things to check

• [X] I have searched the existing issues for this bug
• [X] To rule out a caching problem I made sure the bug also happens in an incognito tab

Bug type

Component

Component name

MudDateRangePicker

What happened?

If you select a range from the previous year and then call ResetAsync() the focus of the control remains on the previously selected period. The DateRange is also unaffected

Expected behavior

The focused period should return to the current period and the DateRange should be cleared

Reproduction link

https://try.mudblazor.com/snippet/cOcyuMwQAuWsDeXL

Reproduction steps

1. Select a date range from 2021
2. Click the button
3. Date range and focused period in control are left unchanged

Relevant log output

No response

Version (bug)

7.6.0

Version (working)

No response

What browsers are you seeing the problem on?

Chrome

On which operating systems are you experiencing the issue?

macOS

Pull Request

• [ ] I would like to do a Pull Request

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[vernou]

Indeed, MudDateRangePicker.ResetAsync has a weird behavior. It resets MudDateRangePicker.Value... that isn't used by the component, because the real value is in MudDateRangePicker.DateRange.

---

@kellyrmartin, maybe MudDateRangePicker.ClearAsync can be a alternative. It resets MudDateRangePicker.DateRange.

[kellyrmartin]

That does in fact clear the date range but the focused period is left untouched