joplin
joplin copied to clipboard
Inconsistent return/newline behaviour in rich text editor
Joplin Desktop Joplin 2.7.14 (dev, linux) Revision: 1b2046f2f (dev)
Linux Mint 20.3
Steps to reproduce
- (Soft breaks turned off)
- Swap to rich text mode + create new note (or swap to a completely empty note)
- Observe return behaviour (always creates
<br>
s, i.e. single spaced lines) - With data on the page, swap notes and come back
- Notice return behaviour is back to normal (return creates a new
<p>
(double space), shift + return creates a<br>
(single space)
I think this is actually happening because of whitespace trimming as you can replicate this in a different way.
- (Soft breaks turned off)
- Swap to rich text mode + create new note
- Observe cursor position:
- Backspace 1x and observe changed position (cursor moves down)
- With cursor in this "second" position, the standard return behaviour is seen. With cursor in the "first" position, the "
<br>
only" behaviour is seen.
Specifically the change is:
Before backspace
<body id="tinymce" class="mce-content-body jop-tinymce" data-id="tinymce-16480286210199659" aria-label="Rich Text Area. Press ALT-0 for help." contenteditable="true">
<div id="rendered-md"><br></div>
</body>
After backspace
<body id="tinymce" class="mce-content-body jop-tinymce" data-id="tinymce-16480286210199659" aria-label="Rich Text Area. Press ALT-0 for help." contenteditable="true">
<p><br data-mce-bogus="1"></p>
</body>
Describe what you expected to happen
Behaviour should remain consistent, until changes are introduced to make TinyMCE respect the soft break settings in its return behaviour it should always create <p>
on return and <br>
on shift + return
Logfile
Nothing relevant in log file
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.
live
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.
Live
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.
Live
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.
Live
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.
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.