Characters are misplaced when pressing enter within Pullquote or Quote block text

[guarani]

Describe the bug

When you create a Pullquote or Quote and you press enter multiple times in the middle of the block's content it starts moving the cursor a character forward and then it puts that character on a new line.

First reported by @jd-alexander here.

To Reproduce

1. Add a Quote block to the editor
2. Add a couple of lines of text
3. Place the cursor somewhere in the middle of that text
4. Press enter repeatedly and notice that as new lines are created, characters are unexpectedly shifted down on to these new lines

Expected behavior
Pressing enter should create blank new lines

Screenshots

Pullquote block	Quote block

Smartphone (please complete the following information):

• Device: Samsung S10
• OS: Android 10
• Version: WordPress for Android 16.6-rc-2

[fluiddot]

👋 I think this issue might be duplicated because I was checking the Multiline components - Test Cases and I spotted that @jd-alexander already created an issue for this.

[fluiddot]

I'm not sure if it's related to the device but I can't manage to reproduce it on my device, here is a video capture:

quote-block-multiline.mp4

Smartphone (please complete the following information):

• Device: Samsung Galaxy S20 FE 5G
• OS: Android 10
• Version: WordPress for Android - Pre alpha - Build 94309

[guarani]

👋 I think this issue might be duplicated because I was checking the Multiline components - Test Cases and I spotted that @jd-alexander already created an issue for this.

Silly me, I'd only checked the Gutenberg Mobile repo and not the Gutenberg repo. Thanks for flagging this as a dupe, closing.

[guarani]

I'm not sure if it's related to the device but I can't manage to reproduce it on my device, here is a video capture:
quote-block-multiline.mp4

Smartphone (please complete the following information):

* Device: Samsung Galaxy S20 FE 5G

* OS: Android 10

* Version: WordPress for Android - Pre alpha - Build 94309

I could reproduce this today on 16.6-rc-2, but maybe you could add that comment to the other issue for better visibility.