Change:
For me, both in Chrome and Edge (without any extensions) the cursor position is off by some characters (a tab?). It seems to happen after reloading the page (hard refresh) or even directly navigating to a challenge URL. to and complete the step. to the next challenge and check the cursor position, it should be fine. the page (hard refresh) and check the cursor position again, it is now off. ! Doesn't seem to happen in Firefox or when I tried it in the JS curriculum. Is this reproducible for anyone else? The only PR I found briefly looking at the commits for the editor is Might be causing this? Edit: I tried reverting the code from the PR and it didn't seem to help so I'm guessing that isn't it. Honestly not sure what is causing it but it seems to have happened between the Feb 28 build and the later production build. Edit 2: For anyone reading this looking for a fix. A normal (soft) page refresh should fix it. Firefox seems unaffected. The cursor position should not be borked after a page reload. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] Forum:
couldn't replicate on edge version 111.0.1661.44 on chrome version 111.0.5563.65, I did have the issue tho, with some area isn't formatted correctly This picture from step 4 on cafe menu !
Make sure it is a hard refresh. I didn't think it would matter but it seems like it does. I will update the repro steps.
Forum report
Yeab, still show sometime in chrome , couldn't replicate on edge Don't need to reload btw, Edit: I forgot to mute system sounds
Added another forum report on this bug. I'm actually surprised we have not yet seen more reports of this bug. But I'm guessing it is because it doesn't seem to trigger when just going through the curriculum using the normal ways of advancing between challenge steps. But man when this bug hits you it makes helping with challenges on the forum an absolute nightmare. I pretty much have to use Firefox (which I don't mind).
Thanks for opening this issue, and for all of the helpful details you provided to reproduce the issue. We've had one report of this issue in the support inbox so far. I wasn't able to reproduce the issue in Chrome on macOS, or in Chromium on an Ubuntu 22.04 VM. But I was able to reproduce the issue with your steps in Chrome on a Windows 11 VM. Once I did opened a challenge in Chrome on Windows and did a hard reload, the cursor position was off when I clicked into the editor or used the arrow keys to move around. The only fix I found is to do a regular reload of the page. Clicking the reset button in the UI, doing a hard reload, or right clicking on the reload button and selecting "Empty Cache and Hard Reload" didn't work on my end. Granted the VMs are ARM versions of Ubuntu and Windows running through Parallels, so that might have some effect on reproducing the issue and the workaround. if you do a regular reload of the page, is the cursor position fixed? Or is the position still off?
You are right, a normal reload does seem to fix it, at least 99% of the time (sometimes it takes two reloads). I guess because the opposite is usually the case I didn't even check it. I didn't think to look before, but the offset of the cursor position in the CSS is different and if you navigate using the arrow keys it doesn't jump the same amount of pixels between keyboard inputs (bugged cursor vs normal).
Wow, this is a weird bug. Just confirming as well that the only time I can trigger this is by doing a hard refresh (Shift + Reload button) using either Chrome or Edge on Win11. Firefox does not seem to be affected on Win11. None of these browsers seem to be affected on Linux. A soft refresh fixes the problem.
Had this happen to me too. Refreshing didn't help, had to move to Firefox for a while.
Could you give us more details about your setup, What browser were you using when you experienced this issue, and what version was it? Also, which OS are you running?
Chrome, latest version, Windows 10

Discussion:
accessibilitySupport: accessibilityMode ? 'on' : 'auto' }); <ins> document.fonts.ready .then(() => monaco.editor.remeasureFonts()) .catch(err => console.error(err)); </ins> // Focus should not automatically leave the 'Code' tab when using a keyboard // to navigate the tablist. if (!isMobileLayout || !isUsingKeyboardInTablist) {