You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Terminal]: 'Save' and 'Discard Changes' button should remain in disabled state until we don't make any changes inside Settings page. #12424
Test Environment:
OS: Windows 11 Version Dev (OS Build 22543.1000)
App: Windows Terminal Preview
Screen Reader: Narrator
Steps to reproduce
Repro Steps:
Open Windows Terminal.
Open Settings page using 'Ctr+,'.
Observe the issue.
User Experience:
Users UX will not be good especially Screen Reader as nothing will happen when they activate 'Save' and 'Discard' as result they will not be able to figure out whether these buttons are actionable or not.
ghost changed the title [-][Terminal]: 'Save' and 'Discard Changes' button should remain in disabled state until we don't make any changes.[/-][+][Terminal]: 'Save' and 'Discard Changes' button should remain in disabled state until we don't make any changes inside Settings page.[/+]on Feb 8, 2022
This depends on #9207. Once that's complete, we can detect if changes have been made, and enable/disable the buttons.
We probably need to use SettingContainer to detect when a change occurred, and update some global view model property s_ChangesDetected = true.
Come to think of it, it would be cleaner to do this with MVVM done, but we could just store that static property off of MainPage (or MainPage's new view model, which we then populate more later). That would be a step in the right direction.
Activity
[-][Terminal]: 'Save' and 'Discard Changes' button should remain in disabled state until we don't make any changes.[/-][+][Terminal]: 'Save' and 'Discard Changes' button should remain in disabled state until we don't make any changes inside Settings page.[/+]carlos-zamora commentedon Feb 8, 2022
This depends on #9207. Once that's complete, we can detect if changes have been made, and enable/disable the buttons.
We probably need to use
SettingContainerto detect when a change occurred, and update some global view model propertys_ChangesDetected = true.Come to think of it, it would be cleaner to do this with MVVM done, but we could just store that static property off of
MainPage(orMainPage's new view model, which we then populate more later). That would be a step in the right direction.akash07k commentedon Feb 16, 2022
Carlos Zamora (@carlos-zamora) Absolutely.
MVVM pattern in settings UI will be a lot appreciated.
It will make the things more flexible
Track and log changes to settings (#17678)