Using Bulleted List, Pressing Enter Twice After 2nd Bullet Goes Down a Newline Instead of Indenting Back To The Left

[TheNightRider12]

Operating system

Windows

Joplin version

3.1.24

Desktop version info

Joplin 3.1.24 (prod, win32)

Client ID: 3ab4e56241704ad0858439088be595f5
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: d581264

Backup: 1.4.2

Current behaviour

Start a bulleted list. Something like "- Hello".
Press Return/Enter.
When a new "-" get's entered, press "Tab" to go to the right.
The new bullet should get moved to the right
Type something in. Such as "test"
Press "Return"/"Enter" twice
Once this is done, the new bullet get's put on another new line instead of being indented to the left, under "Hello".
If you press Return/Enter a second time, the new bullet then gets put under "Hello". But it requires a second press of Enter/Return instead of just one.

Expected behaviour

After pressing return the first time from the "Test" bullet, the bullet point should get indented to the left. Instead of having to press Enter twice to get the bullet to indent back to the left.
I have included a screenshot

Logs

No response

[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.

[TheNightRider12]

Issue is still occurring

[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.