1. Open the C# Sandbox editor.
2. Try to type code using the keyboard.
3. Observe that nothing is entered.
4. Try using the delete/backspace key.
Expected Output
The editor should accept keyboard input and allow the user to write and edit code.
Actual Output
The editor does not respond to keyboard input. The user cannot type any code. However, the delete/backspace key still works. The issue appeared after the Spanish translation update � before the translation, the sandbox was working correctly (there was a previous bug that had been fixed).
Suggested Priority
Critical ? Completely blocks the core functionality of the sandbox. Users cannot practice coding, making the C# lessons unusable.
Additional Notes
This appears to be a regression caused by the recent i18n/translation changes. The fact that delete works but insert doesn't suggests an event handler or focus issue introduced during the localization update. The sandbox was previously functional before the translation changes.
Title: Bug: C# Sandbox - Cannot type code, keyboard input unresponsive
Severity: Critical
Mode: C# Sandbox
Lesson ID / File: C# Sandbox editor
Environment: Browser (specify version), OS (specify version)
Date/Time: 2026-05-22
Source Code
(Not applicable � editor/input issue)
Steps to Reproduce
1. Open the C# Sandbox editor.
2. Try to type code using the keyboard.
3. Observe that nothing is entered.
4. Try using the delete/backspace key.
Expected Output
The editor should accept keyboard input and allow the user to write and edit code.
Actual Output
The editor does not respond to keyboard input. The user cannot type any code. However, the delete/backspace key still works. The issue appeared after the Spanish translation update � before the translation, the sandbox was working correctly (there was a previous bug that had been fixed).
Suggested Priority
Critical ? Completely blocks the core functionality of the sandbox. Users cannot practice coding, making the C# lessons unusable.
Additional Notes
This appears to be a regression caused by the recent i18n/translation changes. The fact that delete works but insert doesn't suggests an event handler or focus issue introduced during the localization update. The sandbox was previously functional before the translation changes.
Triage update: this was reported against v2026.05.17a, when the sandbox used the CodeMirror editor. Since then every editor surface in the platform (including the C# sandbox) was migrated to a shared Monaco-based editor (app-monaco-editor via the language-runner shell). The original symptom — character keys swallowed while Backspace still worked — was a CodeMirror/i18n-era input-handling regression that does not exist in the Monaco wrapper, which uses Monaco's standard onDidChangeModelContent keyboard pipeline.
This is very likely resolved by the migration (same situation as #164). Since this is marked Critical, could you re-verify typing in the C# sandbox against the latest deploy and confirm? If it still reproduces on Monaco, please add browser + OS and I'll dig in with that repro.
Triage update: this was reported against **v2026.05.17a**, when the sandbox used the CodeMirror editor. Since then every editor surface in the platform (including the C# sandbox) was migrated to a shared Monaco-based editor (`app-monaco-editor` via the language-runner shell). The original symptom — character keys swallowed while Backspace still worked — was a CodeMirror/i18n-era input-handling regression that does not exist in the Monaco wrapper, which uses Monaco's standard `onDidChangeModelContent` keyboard pipeline.
This is very likely resolved by the migration (same situation as #164). Since this is marked Critical, could you re-verify typing in the C# sandbox against the latest deploy and confirm? If it still reproduces on Monaco, please add browser + OS and I'll dig in with that repro.
Update: two separate fixes that could each explain this have now shipped to master:
The editor migration to the shared Monaco wrapper (replacing the CodeMirror/i18n-era input pipeline this was reported against), and
An app-wide input-capture leak fix — games (space-game/hexatile in PR #61, Minecraft/wasm-voxel in PR #62) were leaking global keydown/mousedown listeners that preventDefault()-ed input across the whole SPA after a game was opened.
Keeping this open pending re-verification since I can't repro it on the current build. Could you confirm typing in the C# Sandbox on the latest deploy? If it still reproduces, please note browser + OS and whether a game was opened earlier in the session, and I'll dig in with that repro.
Update: two separate fixes that could each explain this have now shipped to `master`:
1. The editor migration to the shared Monaco wrapper (replacing the CodeMirror/i18n-era input pipeline this was reported against), and
2. An app-wide input-capture leak fix — games (space-game/hexatile in PR #61, Minecraft/`wasm-voxel` in PR #62) were leaking global `keydown`/`mousedown` listeners that `preventDefault()`-ed input across the whole SPA after a game was opened.
Keeping this open pending re-verification since I can't repro it on the current build. Could you confirm typing in the C# Sandbox on the latest deploy? If it still reproduces, please note browser + OS and whether a game was opened earlier in the session, and I'll dig in with that repro.
Verified against current master code (source-of-truth check, not just a deploy re-test):
Editor pipeline — the C# sandbox now hosts app-monaco-editor (libraries/platform/monaco-editor/src/lib/monaco-editor.component.ts). Typing flows through Monaco's standard onDidChangeModelContent -> ngModel chain; the only thing that disables typing is the explicit [readonly]/setDisabledState input, which the sandbox doesn't set. The CodeMirror/i18n-era input handler this was reported against no longer exists.
App-wide capture leak — the global keydown/mousedown listeners that games (space-game, hexatile, Minecraft/wasm-voxel) leaked and preventDefault()-ed across the whole SPA were torn down in PR #61 and PR #62, both merged to master.
Both independent root causes are gone in the current build, so closing as resolved. If typing in the C# sandbox still fails on the latest deploy, please reopen with browser + OS and whether a game was opened earlier in the session, and I'll repro from there.
Verified against current `master` code (source-of-truth check, not just a deploy re-test):
1. **Editor pipeline** — the C# sandbox now hosts `app-monaco-editor` (`libraries/platform/monaco-editor/src/lib/monaco-editor.component.ts`). Typing flows through Monaco's standard `onDidChangeModelContent` -> `ngModel` chain; the only thing that disables typing is the explicit `[readonly]`/`setDisabledState` input, which the sandbox doesn't set. The CodeMirror/i18n-era input handler this was reported against no longer exists.
2. **App-wide capture leak** — the global `keydown`/`mousedown` listeners that games (space-game, hexatile, Minecraft/`wasm-voxel`) leaked and `preventDefault()`-ed across the whole SPA were torn down in PR #61 and PR #62, both merged to `master`.
Both independent root causes are gone in the current build, so closing as resolved. If typing in the C# sandbox still fails on the latest deploy, please reopen with browser + OS and whether a game was opened earlier in the session, and I'll repro from there.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Source Code
(Not applicable � editor/input issue)
Steps to Reproduce
Expected Output
The editor should accept keyboard input and allow the user to write and edit code.
Actual Output
The editor does not respond to keyboard input. The user cannot type any code. However, the delete/backspace key still works. The issue appeared after the Spanish translation update � before the translation, the sandbox was working correctly (there was a previous bug that had been fixed).
Suggested Priority
Critical ? Completely blocks the core functionality of the sandbox. Users cannot practice coding, making the C# lessons unusable.
Additional Notes
This appears to be a regression caused by the recent i18n/translation changes. The fact that delete works but insert doesn't suggests an event handler or focus issue introduced during the localization update. The sandbox was previously functional before the translation changes.
Triage update: this was reported against v2026.05.17a, when the sandbox used the CodeMirror editor. Since then every editor surface in the platform (including the C# sandbox) was migrated to a shared Monaco-based editor (
app-monaco-editorvia the language-runner shell). The original symptom — character keys swallowed while Backspace still worked — was a CodeMirror/i18n-era input-handling regression that does not exist in the Monaco wrapper, which uses Monaco's standardonDidChangeModelContentkeyboard pipeline.This is very likely resolved by the migration (same situation as #164). Since this is marked Critical, could you re-verify typing in the C# sandbox against the latest deploy and confirm? If it still reproduces on Monaco, please add browser + OS and I'll dig in with that repro.
Update: two separate fixes that could each explain this have now shipped to
master:wasm-voxelin PR #62) were leaking globalkeydown/mousedownlisteners thatpreventDefault()-ed input across the whole SPA after a game was opened.Keeping this open pending re-verification since I can't repro it on the current build. Could you confirm typing in the C# Sandbox on the latest deploy? If it still reproduces, please note browser + OS and whether a game was opened earlier in the session, and I'll dig in with that repro.
Verified against current
mastercode (source-of-truth check, not just a deploy re-test):app-monaco-editor(libraries/platform/monaco-editor/src/lib/monaco-editor.component.ts). Typing flows through Monaco's standardonDidChangeModelContent->ngModelchain; the only thing that disables typing is the explicit[readonly]/setDisabledStateinput, which the sandbox doesn't set. The CodeMirror/i18n-era input handler this was reported against no longer exists.keydown/mousedownlisteners that games (space-game, hexatile, Minecraft/wasm-voxel) leaked andpreventDefault()-ed across the whole SPA were torn down in PR #61 and PR #62, both merged tomaster.Both independent root causes are gone in the current build, so closing as resolved. If typing in the C# sandbox still fails on the latest deploy, please reopen with browser + OS and whether a game was opened earlier in the session, and I'll repro from there.