I am writing a syntax highlighter. The highlighter should update the highlighting immediately while entering text and navigating with the arrow keys.
The problem I'm facing is that when the 'keypress' event is fired, you still get the old position of the text cursor via window.getSelection()
.
Example:
function handleKeyEvent(evt) {
console.log(evt.type, window.getSelection().getRangeAt(0).startOffset);
}
var div = document.querySelector("div");
div.addEventListener("keydown", handleKeyEvent);
div.addEventListener("keypress", handleKeyEvent);
div.addEventListener("input", handleKeyEvent);
div.addEventListener("keyup", handleKeyEvent);
<div contenteditable="true">f<span class="highlight">oo</span></div>
In the example, place the caret before the word 'foo', then press → (the Right Arrow key).
Within the console of your favorite DevTool you'll see the following:
keydown 0
keypress 0
keyup 1
That 0
besides keypress
is obviously the old caret position. If you hold down → a bit longer, you'll get something like this:
keydown 0
keypress 0
keydown 1
keypress 1
keydown 1
keypress 1
keydown 2
keypress 2
keyup 2
What I want to get is the new caret position like I would get it for 'keyup' or 'input'. Though 'keyup' is fired too late (I want to highlight the syntax while the key is pressed down) and 'input' is only fired when there is actually some input (but → doesn't produce any input).
Is there an event that is fired after the caret position has changed and not only on input? Or do I have to calculate the position of the text cursor and if so, how? (I assume this can get quite complicated when the text wraps and you press ↓ (the Down Arrow key).)
You can use
setTimeout
to process thekeydown
event asynchronously:That method addresses the key processing problem. In your example, you also have a
span
element inside of thediv
, which alters the position value returned byHere's a solution correcting the position using the 'keydown' event:
Unfortunately this solution as is has several flaws:
<span>
in the example, it doesn't provide the correctstartOffset
nor the correctstartContainer
.And there are probably more issues I didn't think of. While it would be possible to handle all those issues, it makes the implementation very complex. So the simple
setTimeout(..., 0)
solution provided by ConnorsFan is definitely preferable until there is an event for caret position changes.