BUG: Firefox trims trailing white space, unexpected cursor behavior

Do you want to request a feature or report a bug?

report a bug

What’s the current behavior?

If a text node ends in a \n when a user presses enter, Firefox trims the whitespace and the cursor stays on the same line. If the user continues typing, the characters appear in the correct location. If the user presses down arrow, the cursor will appear on the correct line.

If I change the event handler from Transforms.insertText(editor, \n) to Transforms.insertText(editor, \n\u2060) (adds a zero width white space) the editor works as expected.

See sandbox: here

Slate: 0.59.0 Browser: Firefox OS: Mac

What’s the expected behavior?

It should move the cursor to the new line as it does on Chrome.

[rsdrsd]

Are there more solutions for this bug?

[JMLX42]

This ckeditor PR might be related:

https://github.com/ckeditor/ckeditor5-engine/pull/1582/files

This code in particular:

function fixGeckoSelectionAfterBr( focus, domSelection ) {
	const parent = focus.parent;

	// This fix works only when the focus point is at the very end of an element.
	// There is no point in running it in cases unrelated to the browser bug.
	if ( parent.nodeType != Node.ELEMENT_NODE || focus.offset != parent.childNodes.length - 1 ) {
		return;
	}

	const childAtOffset = parent.childNodes[ focus.offset ];

	// To stay on the safe side, the fix being as specific as possible, it targets only the
	// selection which is at the very end of the element and preceded by <br />.
	if ( childAtOffset && childAtOffset.tagName == 'BR' ) {
		domSelection.addRange( domSelection.getRangeAt( 0 ) );
	}
}