Broken rendering with lists

[miguelammatos]

Operating system

macOS

Joplin version

3.2.13

Desktop version info

Joplin 3.2.13 (prod, darwin)

Client ID: 8df9ea3991034b0392c378ccf2258ecf
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: a898e17

Backup: 1.4.2
Email Plugin: 1.0.0
Freehand Drawing: 2.14.0
Joplin DDDot: 0.4.2
macOS theme: 1.5.7

Current behaviour

The rendering is broken when using lists, after a line-break it is no longer possible to place the cursor on the text after the break.
The attached video demonstrates the behavior.
It can always be reproduced both with the regular editor and the Vim version.

When editing the note in an external editor the contents looks fine (i.e. there are no unexpected characters) so this seems to be a rendering issue.

This seems to be similar to #11976

joplin_bug.mov

Expected behaviour

The list rendering and cursor placement should work properly.

Logs

I can provide any necessary logs or test beta versions if necessary.

[github-actions]

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.

[miguelammatos]

As of the latest version 3.2.13 in macos the problem still persists.

[github-actions]

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]

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.