Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Screenshot viewer has no close button with experimental integrated Windows header enabled

Open
#4,101 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Domain
desktop

Research direction

Reproduce the screenshot viewer on Windows with the experimental integrated Windows header enabled, then locate the viewer implementation and its existing Escape dismissal behavior. Add a visible, clickable close control that also works with the integrated header, while preserving Escape; verify by repeating the reported steps.

Written by the indexing model from the issue text.

Description

Short summary

The screenshot viewer has no visible close button when the experimental integrated Windows header feature is enabled.

Affected version or release

Not provided.

Installation context

GitHub Copilot app on Windows, with the experimental integrated Windows header enabled.

What happened?

Opening a screenshot displays a viewer without a close button. The only known way to dismiss the screenshot is to press Escape, leaving no visible mouse-accessible way to close it.

Steps to reproduce
  1. On Windows, enable the experimental integrated Windows header feature.
  2. Open a screenshot in the app.
  3. Observe that the screenshot viewer has no visible close button.
Expected behavior

The screenshot viewer should have a visible, clickable close button, including when the experimental integrated Windows header is enabled. Escape should remain available as a keyboard shortcut.

Additional context

Workaround: press Escape to dismiss the screenshot.

Dominant language
No language data
Stars
2.1k
Forks
157
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/app

All issues in github/app

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.