I’ve noticed that when writing text on LessWrong, there is a tendency for the cursor to glitch out and jump to the beginning of the text. I don’t have the same problem on other websites. This most often happens after I’ve clicked to try to insert the cursor in some specific spot. The cursor briefly shows where I clicked, but then the page lags slightly, as if loading something, and the cursor jumps to the beginning.
The way around this I’ve found is to click once. Wait to see if the cursor jumps away. If so, click again and hope. Only start typing once you’ve seen multiple blinks at the desired location. Annoying!
We used to have a bug like this a long time ago, it was related to a bug at the intersection of our rich-text editor library and our upgrade from React 17 to React 18 (our front-end framework). I thought that we had fixed it, and it’s definitely much less frequent than it used to be, but it’s plausible we are having a similar bug.
It’s annoyingly hard to reproduce, so if you or anyone else finds a circumstance where you can reliably trigger it, that would be greatly appreciated.
I’ve noticed that when writing text on LessWrong, there is a tendency for the cursor to glitch out and jump to the beginning of the text. I don’t have the same problem on other websites. This most often happens after I’ve clicked to try to insert the cursor in some specific spot. The cursor briefly shows where I clicked, but then the page lags slightly, as if loading something, and the cursor jumps to the beginning.
The way around this I’ve found is to click once. Wait to see if the cursor jumps away. If so, click again and hope. Only start typing once you’ve seen multiple blinks at the desired location. Annoying!
We used to have a bug like this a long time ago, it was related to a bug at the intersection of our rich-text editor library and our upgrade from React 17 to React 18 (our front-end framework). I thought that we had fixed it, and it’s definitely much less frequent than it used to be, but it’s plausible we are having a similar bug.
It’s annoyingly hard to reproduce, so if you or anyone else finds a circumstance where you can reliably trigger it, that would be greatly appreciated.