Fix sticky cursor resulting in reverse typing if the editable is not the activeElement in the document.

[urbanspr1nter]

This PR attempts to fix an issue with cases where "reverse typing" effect still occurs. This is caused by a selection not being updated when an input event occurs. The selection seems to not be updated because the document.activeElement in DOM is not the correct element.

There are cases where the editable visually looks focused, but in reality the active element is some other element as it may have stole focus while the editable was active at some point. This can be caused by a manual dispatch of a blur event for example.

We can actually simulate it like this:

setTimeout(() => { 
	const editable = document.querySelector("div[contenteditable=true]");
	editable.dispatchEvent(new FocusEvent("blur"));

	console.log("BLUR!")
}, 5000);

If the editable is currently in focus, but the blur happens later, the active element in the document is not updated properly, and can end up having a selection which is out of sync with the characters being rendered into the editable. (It just sticks and never moves forward).

An example:

Something like this can also be seen in the Safari web browser where a a button click can cause the issue to occur:

Source

After fix:

Browsers tested on web (manual):

• Google Chrome
• Safari
• Firefox

Suggested merge commit message (convention)

Type: (engine): Force the editable to be focused if the active element is not the editable when an input event occurs. Closes #15182, #14702 .

---

Additional information

For example – encountered issues, assumptions you had to make, other affected tickets, etc.

[urbanspr1nter]

Thoughts on this?

[Witoso]

@urbanspr1nter thanks for the PR, and sorry for the late reply. A bit hectic down here 😊  @niegowski will soon take a look at a couple of problems regarding typing. We will take a look at this as well!

[Witoso]

Hey @urbanspr1nter, we prepared a separate PR, as we are merging all typing improvements PRs to one branch. Thanks for the contribution, we used your solution but placed it in a slightly different place. Check #16267 for details. :)

[urbanspr1nter]

Thanks! Of course, I'll always leave it to the experts. :)