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

History: Restoring a note breaks the note list #1772

Closed
rachelmcr opened this issue Dec 10, 2019 · 1 comment · Fixed by #1774
Closed

History: Restoring a note breaks the note list #1772

rachelmcr opened this issue Dec 10, 2019 · 1 comment · Fixed by #1774
Labels
bug Something isn't working
Milestone

Comments

@rachelmcr
Copy link
Member

Expected

I expect that I can restore a past revision of a note and continue using the app.

Observed

After restoring a past revision of a note, I can't open any other notes in the note list. I can click on them and they are highlighted in the list, but they don't open in the editor.

The issue persists until I relaunch the app.

Reproduced

  1. Open the app.
  2. Select a note that has a history (past revisions).
  3. Open the revision selector.
  4. Select and restore a past revision.
  5. Select a different note in the notes list and notice that it doesn't open in the editor.
Make Model OS Version App Version
Windows VirtualBox VM Win10 1.13.0-beta1
Mac Macbook Pro (2017) macOS 10.15.1 1.13.0-beta1

I can also reproduce the issue on macOS 10.15.1 in Chrome 78.0.3904.108 at https://app.simplenote.com/ (running version 1.12.0 according to the About section).

cc @belcherj

@rachelmcr rachelmcr added the bug Something isn't working label Dec 10, 2019
@rachelmcr
Copy link
Member Author

I can't reproduce this in version 1.12.0 of the Windows desktop app, so I think this is a regression in this version (despite what the version number on the web app is telling me).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants