joplin icon indicating copy to clipboard operation
joplin copied to clipboard

Input fields all over the application are disabled after showing message dialog

Open ab-elhaddad opened this issue 10 months ago • 4 comments

Operating system

Windows

Joplin version

2.14.20, 3.0.2

Desktop version info

No response

Current behaviour

  1. Open application settings
  2. Write anything in any input field without saving it
  3. Switch to the encryption screen
  4. A dialog with warning is shown (take any action doesn't matter)
  5. All input fields in the application are disabled
  6. Switch to another window and come back again to joplin
  7. All input fields work normally

https://github.com/laurent22/joplin/assets/113056556/9de376cb-cdc2-4d68-bf5a-39ac7d9164f3

https://github.com/laurent22/joplin/assets/113056556/10b8b29c-0854-4e7d-bd1b-bc8d0f6acbd0

Expected behaviour

Input fields should work all the time and not be affected by a warning dialog

Logs

No response

ab-elhaddad avatar Apr 02 '24 17:04 ab-elhaddad

I cannot replicate this on macOS

laurent22 avatar Apr 02 '24 17:04 laurent22

I couldn't replicate it on Ubuntu either. But I replicated it on several Windows machines. I am not sure why does it appears only on Windows.

ab-elhaddad avatar Apr 03 '24 04:04 ab-elhaddad

I can replicate it when I run Joplin code on my pc locally... Cannot replicate it in the downloaded Joplin desktop app.

Operating system - PopOS (linux)

Aitchessbee avatar Apr 14 '24 10:04 Aitchessbee

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? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. 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.

github-actions[bot] avatar May 14 '24 16:05 github-actions[bot]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.

github-actions[bot] avatar May 22 '24 16:05 github-actions[bot]