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

Escape key will close Peak #26178

Closed
mybabysexy opened this issue May 24, 2023 · 3 comments
Closed

Escape key will close Peak #26178

mybabysexy opened this issue May 24, 2023 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mybabysexy
Copy link

Description of the new feature / enhancement

Current: Must use Alt+F4 or manually close by pressing Close (X) button

Enhancement: Like on MacOS, pressing Esc key will close Peak

Scenario when this would be used?

I use Peak because I want to view the file quickly, but manually closing Peak view takes same time as open the file directly

Supporting information

No response

@mybabysexy mybabysexy added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label May 24, 2023
@bartonnen
Copy link

I found that you can also use the activation shortcut again to close the window (default Ctrl-Space).

But it should also accept Esc to close.

I didn't even realise there was an "X" close button, they're in white and don't show up until you hover over them (with windows in a light theme).

@jaimecbernardo
Copy link
Collaborator

/dup #26137

@microsoft-github-policy-service
Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels May 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants