Skip to content

[Terminal]: 'Save' and 'Discard Changes' button should remain in disabled state until we don't make any changes inside Settings page. #12424

Open

Description

Windows Terminal version

1.13.10336.0

Windows build number

10.0.22543.1000

Other Software

Test Environment:
OS: Windows 11 Version Dev (OS Build 22543.1000)
App: Windows Terminal Preview
Screen Reader: Narrator

Steps to reproduce

Repro Steps:

  1. Open Windows Terminal.
  2. Open Settings page using 'Ctr+,'.
  3. 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.

Attachments:
'Save' and 'Discard Changes' button should remain in disabled state until we don't make any changes..zip

Expected Behavior

'Save' and 'Discard Changes' button should remain in disabled state until we don't make any changes inside Setting page.

Actual Behavior

'Save' and 'Discard Changes' buttons are in active state even if they are not actionable inside Setting page.

Activity

  1. ghost added
    Issue-BugIt either shouldn't be doing this or needs an investigation.
    on Feb 8, 2022
  2. ghost added on Feb 8, 2022
  3. ghost added
    HCL-E+DAccessibility tracking
    on Feb 8, 2022
  4. ghost added
    A11yUsableAccessibility tracking
    on Feb 8, 2022
  5. ghost added
    A11yCOAccessibility tracking
    on Feb 8, 2022
  6. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Feb 8, 2022
  7. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Feb 8, 2022
  8. 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
  9. added
    Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.
    and removed
    Issue-BugIt either shouldn't be doing this or needs an investigation.
    on Feb 8, 2022
  10. added and removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Feb 8, 2022
  11. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Feb 8, 2022
  12. carlos-zamora commented on Feb 8, 2022

    @carlos-zamora

    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.

  13. akash07k commented on Feb 16, 2022

    @akash07k

    Carlos Zamora (@carlos-zamora) Absolutely.
    MVVM pattern in settings UI will be a lot appreciated.
    It will make the things more flexible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A11yCOAccessibility trackingA11yUsableAccessibility trackingArea-AccessibilityIssues related to accessibilityArea-SettingsUIAnything specific to the SUIHCL-E+DAccessibility trackingHCL-WindowsTerminalAccessibility trackingIssue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Priority-3A description (P3)Product-TerminalThe new Windows Terminal.WindowsTerminal_Win32

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions