Skip to content

[Functional-Command Palette]- User is not able to move back from the New Tab sub menu as there is no functionality provided to move out of Sub menu. #7910

Closed

Description

@DasaradhaKamjula

User Experience:
Users who rely on screen reader/Keyboard will not be able to navigate efficiently if there is no option provided to move out of Sub menu

Test Environment:
App: Windows Terminal Preview
Feature: Command Palette
Screen Reader: Narrator
OS: Win 10 2004 Build (19041.508)

Repro Steps:
1.Open Windows terminal Preview app
2.Open Command Palette using shortcut (Ctrl+shift+p)
3.Search for New tab command in the search field
4.Navigate to New Tab list item having sub menu and activate it .
5.Verify whether there is any option provided to move back.

Actual:
User is not able to move back from the sub menu as there is no functionality provided to move out of Sub menu.

Note: Same issue repro for Split pane and Set color scheme controls having Sub menu

Expected:
Functionality should be provided to move back from sub menu by using back button or some other way other wise user has to close command palette and open it again to get all commands

Activity

  1. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Oct 13, 2020
  2. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Oct 13, 2020
  3. added
    Area-UserInterfaceIssues pertaining to the user interface of the Console or Terminal
    Issue-TaskIt's a feature request, but it doesn't really need a major design.
    and removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Oct 13, 2020
  4. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Oct 13, 2020
  5. zadjii-msft commented on Oct 13, 2020

    @zadjii-msft
    Member

    This is a really good idea

  6. ghost added
    In-PRThis issue has a related PR
    on Oct 27, 2020
  7. ghost closed this as completedin #8051on Nov 5, 2020
  8. ghost removed
    In-PRThis issue has a related PR
    on Nov 5, 2020
  9. ghost added a commit that references this issue on Nov 5, 2020
    341bb4f
  10. 2 remaining items

  11. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Nov 5, 2020
  12. DHowett commented on Nov 5, 2020

    @DHowett
    Member

    DasaradhaKamjula This has been fixed pending future release. I've reopened the bug so that you can track it.

  13. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Nov 5, 2020
  14. zadjii-msft commented on May 20, 2021

    @zadjii-msft
    Member

    Chandresh1007 If this is confirmed as fixed, can we close this issue now?

  15. Priyanka-Chauhan123 commented on Jun 23, 2021

    @Priyanka-Chauhan123
    Collaborator

    Issue is fixed. Verified on Windows terminal version: 1.8.1521.0 and OS version: Win 10 build 21390.2025. Hence, closing the bug.

  16. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Jun 23, 2021
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

    Area-CmdPalCommand Palette issues and featuresArea-UserInterfaceIssues pertaining to the user interface of the Console or TerminalFixedIssues assigned by the accessibility team that have been fixed.HCL-E+DAccessibility trackingHCL-WindowsTerminalAccessibility trackingImpact-ComplianceIt gotta be this way.Issue-TaskIt's a feature request, but it doesn't really need a major design.Needs-Tag-FixDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.WindowsTerminal_Win32

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions