Shift+Enter results in unintentional page shift

Describe the issue:

  • When we are in the process of writing an article in the Content model, we sometimes want to use the Shift+Enter key combination to place text in a new line. However, when we do that in the richtext or in a richtext_box the current position where the text cursor is, jumps to a couple of paragraph above. The text cursor however remains on the same place, so when we then type text, we can’t see the changes because the visible position in the content has changed.

    Also, when adding an image box or other type of box, the position of view also changes, so we have to scroll back to the original position where the image box was added. And sometimes placing an Enter in the text makes it jump to another position, esepcially when the text is very long.

    Not sure if this is a wide-spread bug, or of anyone else has come forward with this, as it is quite specific.

Screen capture included

Hello @mgamble,

I tried to replicate this, both in a demo project of my own and in your id-nl env, but I wasn’t quite able to. I’m thinking it only happens under particular combinations of certain kinds of text fields…

Could you please let me know the specific record & field it’s happening in? You can email us at support@datocms.com or PM me here if it’s private.

i.e., I think it requires a specific order of field / block / text fields to happen, and I need to see it in your real project (or a reproduction demo project) in order to track it down, please :folded_hands:

Thank you and sorry about that!

Nevermind, sorry, I was able to make it happen after all! It only seems to happen in some browsers so far, namely Chrome. Firefox and Safari do not seem to be affected.

I’ll let the developers know. Thank you!

Hi @roger Thank you so much for investigating this. In our case, apart from Chrome, the problem also occurs in Edge and Opera. Coincidentally, they are all part of the Chromium codebase, so the underlying problem must be related to that.

1 Like

Yes, it looks like a Blink/Chromium issue. Sorry about that. I’ll report back once we have a fix!

No need to apologize, i’m glad you’e looking into it :slightly_smiling_face:

We will await a fix, thanks again for checking!

Best regards,

Mark