Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

It's possible to lose changes in Brackets #7794

Closed
JeffryBooher opened this issue May 8, 2014 · 3 comments
Closed

It's possible to lose changes in Brackets #7794

JeffryBooher opened this issue May 8, 2014 · 3 comments

Comments

@JeffryBooher
Copy link
Contributor

The double close mechanism in Brackets could cause you to lose unsaved changes.

  1. Start Brackets
  2. Open the starter project
  3. Make a change
  4. Click the close button to quit Brackets
  5. Prompt to save (click yes),
    ==> changes are saved but brackets doesn't quit
  6. Make some more changes
  7. Click the close button to quit brackets
    ==> Not prompted to save unsaved changed and brackets shutsdown

This was filed as #5714 but the unsaved changes problem wasn't fully recognized at the time.

@pthiess
Copy link
Contributor

pthiess commented May 8, 2014

Reviewed - high priority / data loss.

@peterflynn
Copy link
Member

@JeffryBooher Rather than having two bugs tracking the same fix, can you move these notes over to #5714 and bump up its priority to match? (and then close this duplicate)

@JeffryBooher
Copy link
Contributor Author

Closing as dup of #5714

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants