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.

Sign up for GitHub

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

Jump to bottom

Store Update of WinTerminal closes open terminals #2910

Closed
wigster opened this issue Sep 26, 2019 · 1 comment
Closed

Store Update of WinTerminal closes open terminals #2910

wigster opened this issue Sep 26, 2019 · 1 comment
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-External For issues that are outside this codebase

Comments

@wigster
Copy link

wigster commented Sep 26, 2019

Environment

Windows 10.0.18362.0 
Windows Terminal version: upgrading 0.5.2661 -> 0.5.2681 (store version)

Steps to reproduce

  • Windows Terminal window open
  • Update available in store found by "Get Updates" in Downloads & Updates
  • Update installs automatically
  • Update kills all open windows without warning

Expected behaviour

WT should not begin update if a Windows is open with potential unfinished work

Other Store apps do not begin update if there are open windows. Instead a user-trigger is required by explicit click on Update button

Actual behaviour

Update occurs leading to potential work loss.
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Sep 26, 2019
@DHowett-MSFT
Copy link
Contributor

I don’t believe terminal can tell the store when it’s in use. Would you mind filing a request on Feedback Hub (in the Windows Store category)? That’ll make sure it gets to the right folks.

@DHowett-MSFT DHowett-MSFT added the Resolution-External For issues that are outside this codebase label Sep 26, 2019
@github-actions github-actions bot mentioned this issue Jun 6, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-External For issues that are outside this codebase
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wigster @DHowett-MSFT