Joplin: [Bug] Undo action in notes exhibits strange behavior

Created on 10 Jun 2019  路  21Comments  路  Source: laurent22/joplin

  • Windows 10
  • Desktop

When Ctrl-Z is pressed, the last action in note should be undone and the prompt should position itself where the change occurs. But it doesn't work when you use buttons in toolbar.
How to reproduce the bug:

  • click on any button of toolbar (Bold, Italic, Hyperlink, code, numbered list, bulleted list, checkbox, Heading, Horizontal rule, Date & time)
  • press Ctrl-Z
  • the prompt never positions itself where change occurs but all the text in the note gets selected
  • in addition, with some buttons, undo doesn't work.

Most helpful comment

This also happens if keyboard shortucts (e.g., Ctrl + B for bold) are used instead of toolbar buttons.

All 21 comments

Confirming same behavior in Linux version 1.0.160.
It does undo each toolbar button but then highlights the entire note text.

This also happens if keyboard shortucts (e.g., Ctrl + B for bold) are used instead of toolbar buttons.

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "backlog" and I will leave it open. Thank you for your contributions.

Not fixed. Do not close. (damn that bot is annoying)

Confirming that this is still happening. Can reproduce across all the desktop platforms - Linux, Windows and Mac.

I just started trying Joplin today and this is the very first annoying thing I noticed. Ctrl-Z loses my focus and brings me to end of document.

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

Still relevant.

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

Please don't close this issue. It's still relevant.

Sooo after 1 year, is this a bug, or an intended behavior ?

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

Not fixed

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

Not fixed.

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

Not fixed.

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

Not fixed.

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

Not fixed.

Was this page helpful?
0 / 5 - 0 ratings