Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when trying to alt+F1 in terminal #191619

Closed
alexr00 opened this issue Aug 29, 2023 · 11 comments
Closed

Error when trying to alt+F1 in terminal #191619

alexr00 opened this issue Aug 29, 2023 · 11 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@alexr00
Copy link
Member

alexr00 commented Aug 29, 2023

Testing #191345

  1. Turn on screen reader accessibility mode.
  2. Open the terminal and focus into it.
  3. alt+F1.
  4. Get a warning "Cannot read properties of undefined (reading 'getAriaLabel')"
  5. Accessible view doesn't open.
@meganrogge
Copy link
Contributor

/duplicate #191591

@vscodenpa vscodenpa added the *duplicate Issue identified as a duplicate of another issue(s) label Aug 29, 2023
@meganrogge
Copy link
Contributor

@alexr00 I cannot repro - could you pls provide the full error stack trace?

@alexr00
Copy link
Member Author

alexr00 commented Aug 29, 2023

I checked, there wasn't an error stack trace in the console.

image

@meganrogge
Copy link
Contributor

Does this only happen in the terminal for you?

@meganrogge
Copy link
Contributor

I'll try on Windows, maybe that's the difference

@meganrogge
Copy link
Contributor

nope doesn't repro for me there either 😢

@alexr00
Copy link
Member Author

alexr00 commented Aug 29, 2023

Yes, only in the terminal. It happens 100% of the time in the terminal as far as I can tell.

@meganrogge
Copy link
Contributor

I see what could lead to this, thanks

@alexr00
Copy link
Member Author

alexr00 commented Aug 29, 2023

I'm also trying to find where it's coming from.

@meganrogge
Copy link
Contributor

meganrogge commented Aug 29, 2023

pretty sure it's coming from here

const kb = this._keybindingService.lookupKeybindings(commandId);
// Run recent command has multiple keybindings. lookupKeybinding just returns the first one regardless of the when context.
// Thus, we have to check if accessibility mode is enabled to determine which keybinding to use.
return this._accessibilityService.isScreenReaderOptimized() ? format(msg, kb[1].getAriaLabel()) : format(msg, kb[0].getAriaLabel());

and for some reason, lookupKeybindings finds two for me which is why I cannot repro whereas it's only finding one for you, so kb[1] is udf

@alexr00
Copy link
Member Author

alexr00 commented Aug 29, 2023

I've just reload, which I though I had already done at least once since encountering the issue, and now I can't repo. I'm not sure what would have changed here.

@github-actions github-actions bot locked and limited conversation to collaborators Oct 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants