macOS Firefox: "Unresponsive" keyboard when going back from next block using keyboard

[eiriarte]

When I move back to a previous block using the keyboard, the cursor goes back, but I can't type right away.

Steps to reproduce the behavior

1. Posts → Add New
2. Write title
3. Write a first paragraph and press ENTER.
4. You are now in the second paragraph. Go back to the first paragraph with LEFT CURSOR key (or BACKSPACE).
5. You are now at the end of the first paragraph. Try to type something. Nothing happens. The cursor is there, but it is not responsive: you can only use keys like ENTER or CURSOR keys.

Notes

• It also happens with headings and quotes, not just paragraphs.
• It seems to work fine in Chrome.

Capture

Versions: WordPress 4.9.8 / Gutenberg 3.8.0
System: macOS 10.11.6
Browser: Firefox 62.0 (64-bit)

[talldan]

Thanks for the report 👍 - I can also reproduce this consistently. No console errors or warnings. I also noticed another thing that may or may not be related in firefox. When backspacing into the previous paragraph block as mentioned above, superfluous <br> elements are created at the end of the paragraph.

edit: This superfluous br issue I mentioned seems quite hard to reproduce and probably unrelated, but I was seeing the data-mce-bogus br element being replaced by multiple normal br elements.

[talldan]

I've done some further debugging on this one and discovered that when functioning correctly the caret is properly placed at the end of the rich text. Calling this.editor.selection.getRng() returns that the selection range is correctly in the paragraph element's text node:

{
  startOffset: 4,
  endOffset: 4,
  startContainer: #text,
  endContainer: #text,
  // ...
}

When reproducing this bug, the range selected is completely different:

{
  startOffset: 0,
  endOffset: 0,
  startContainer: <br data-mce-bogus="1">,
  endContainer: <br data-mce-bogus="1">,
  // ...
}

So it looks as though we might be attempting to type within the br element.

I can't continue looking into this right now, but hopefully this information is useful.

[ellatrix]

@eiriarte I think #11287 fixes this issue as well.

[youknowriad]

closed by #11287