Quote Block: Pasting on a new line doesn't work

[zdenys]

Steps to reproduce the behavior

1. Add a Quote Block
2. Type in some text
3. Press Enter/Return key to create a new line within the same block
4. Copy any text from another block, from outside WordPress.com, or the very text you just typed
5. Try pasting it on the new line within Quote Block

What I expected to happen

See the pasted text

What actually happened

No text is pasted

Context

Browser / OS version

Any

Is this specific to the applied theme? Which one?

No (Tested on Twenty Twenty and Blank Canvas so far)

Does this happen on simple or atomic sites or both?

Tested on Simple only so far

Is there any console output or error text?

No

Level of impact (Does it block purchases? Does it affect more than just one site?)

Low

Reproducibility (Consistent, Intermittent) Leave empty for consistent.

Consistent

Screenshot / Video: If applicable, add screenshots to help explain your problem.

Quote.Block.Bug.Cannot.Paste.On.A.New.Line.mov

[zdenys]

Possibly the underlying issue could be related to how multiple lines are handled in the Quote Block which is happening here #47526

[mrfoxtalbot]

Thank you, @zdenys!

Ok, so this seems to be coming from the core editor but only seems to be happening with the plugin active (10.8).

I looked it up and it seems to be related to this WordPress/gutenberg#32468 (but affecting quote blocks instead of lists).

I am leaving this open for "traceability" but there is a fix in place here WordPress/gutenberg#32527

[davipontesblog]

@mrfoxtalbot the PR WordPress/gutenberg#32527 seems to be merged, I am moving this back to triaging to see if we can verify if the issue is now fixed. If so, please close it when that happens :)

[mrfoxtalbot]

Thank you @davipontesblog! I just retested this on a simple site and I can still reproduce the problem.

In fact, I noticed that the exact same thing is happening on list blocks.

I am getting this error:

Uncaught TypeError: Cannot read property 'length' of undefined

at Xu (??-eJylzrEOwjAMBNAfInELqBID4ltIYhW3qV05Tgt/T1dGlOGG00lPB/vqorAhG6y5jsQFxnrUgDoeiyJsfedvvoNQKSeY8RPkqcmVl6jFagWIE779QuyncoJ/QRajiK2KyYzsMhVrhKrmRmEXTVEqtz4JWeLsMJGJ/lCP5d4P52t35DJMX374oc0=:66)

at HTMLDivElement.n (??-eJylzrEOwjAMBNAfInELqBID4ltIYhW3qV05Tgt/T1dGlOGG00lPB/vqorAhG6y5jsQFxnrUgDoeiyJsfedvvoNQKSeY8RPkqcmVl6jFagWIE779QuyncoJ/QRajiK2KyYzsMhVrhKrmRmEXTVEqtz4JWeLsMJGJ/lCP5d4P52t35DJMX374oc0=:66)

[Robertght]

I think this is the same issue as this one: #54106

I'm voting in closing this one in favor of the above for now.

[mrfoxtalbot]

I agree, @Robertght. Thank you for spotting the duplicate. Closing in favor of #54106 I have added the same tags. this issue had on the new one.