You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Let me type and edit a name in the browser game #28
I want to click a text box, type a name, select it with Command-A on Mac, and replace it. Text input should be enabled while I am editing and disabled when I leave the field or tab.
In the reproduced Chrome case, Backspace worked but letters did not appear. Windy blocked the browser event that delivers letters, and it also lacked the Mac Command-key mapping. Fixing those paths makes ordinary name editing usable.
PR #9 uses the fixes from Windy #194 and follows the example field's focus. Basic typing, focus changes, and a held Command-A followed by replacement were checked in Mac Chrome. This gathers Command-key support #31 and text-entry focus #33.
The comments here also raise a possible native input-method problem when text input is left enabled. That still needs a native reproduction; the browser checks do not establish a native fix. Renaming Windy's text-input setting is not required to fix these behaviors.
It used to work in normal windy and silky and there might be a rune input issue with polyworld. Somehow AI likes to set rune input to true and then this enables IME etc so I think something in polyworld broke this we'll root cause this
I reproduced the browser failure with current upstream Windy: Backspace worked, but typing “Nora” left the name empty. The browser recorded cancelled keydown events and no corresponding keypress events. With the pinned fix, the same real keyboard input produced “Nora.”
I also removed the gallery’s unconditional text-input setting. PR #9 now enables it only while the name field is focused and disables it when leaving the field or tab. The focused control test and Chrome check pass.
Your native IME concern is separate and remains unverified. I narrowed the issue accordingly; this browser result does not establish that native text input is fixed. Renaming Windy’s public setting would also be a separate upstream API change.
The broader browser audit found two more distinct cases. Windy did not map the Mac Command keys, so even a held Command-A failed to select a name. PR #194 now maps them: in the same visible field, “Hello” is selected and replaced with “R.” Polyworld #9 now pins that commit.
A shortcut pressed and released entirely between rendered frames can still be missed because the text control observes the current modifier state after it has been released. That timing problem remains open; the Command-key mapping does not fix it. Ordinary typing, focus behavior, and a held shortcut have separate browser evidence. Native IME and clipboard behavior remain unverified.
Fixed upstream by merged Windy #196 and Silky #69. Windy now delivers browser letters and Command-key/modifier events correctly. Silky automatically manages focused text entry and preserves fast shortcuts through its ordered input queue. The Silky web demo passed manual typing, replacement, focus, and keyboard-control checks, and the maintainer confirmed it works.
Closing this separate browser bug tracker as fixed upstream. Polyworld main and PR #9 still pin older dependencies; migration to Silky 0.2.0 and verification in the actual gallery remain tracked in #26 and PR #9.
The possible native input-method concern remains unverified and is recorded in #26. These changes do not claim to implement IME or clipboard fixes.
Activity
[-]I want to type names into browser game menus[/-][+]I can’t type into text boxes in the browser[/+]relh commentedon Sep 9, 2026
It used to work in normal windy and silky and there might be a rune input issue with polyworld. Somehow AI likes to set rune input to true and then this enables IME etc so I think something in polyworld broke this we'll root cause this
relh commentedon Sep 9, 2026
runeEnabled is a bad name we should just change it to text box enabled = true
[-]I can’t type into text boxes in the browser[/-][+]Let me type into the browser game’s text boxes[/+]relh commentedon Sep 9, 2026
I reproduced the browser failure with current upstream Windy: Backspace worked, but typing “Nora” left the name empty. The browser recorded cancelled keydown events and no corresponding keypress events. With the pinned fix, the same real keyboard input produced “Nora.”
I also removed the gallery’s unconditional text-input setting. PR #9 now enables it only while the name field is focused and disables it when leaving the field or tab. The focused control test and Chrome check pass.
Your native IME concern is separate and remains unverified. I narrowed the issue accordingly; this browser result does not establish that native text input is fixed. Renaming Windy’s public setting would also be a separate upstream API change.
relh commentedon Sep 9, 2026
The broader browser audit found two more distinct cases. Windy did not map the Mac Command keys, so even a held Command-A failed to select a name. PR #194 now maps them: in the same visible field, “Hello” is selected and replaced with “R.” Polyworld #9 now pins that commit.
A shortcut pressed and released entirely between rendered frames can still be missed because the text control observes the current modifier state after it has been released. That timing problem remains open; the Command-key mapping does not fix it. Ordinary typing, focus behavior, and a held shortcut have separate browser evidence. Native IME and clipboard behavior remain unverified.
[-]Let me type into the browser game’s text boxes[/-][+]Let me type a name in the browser game[/+][-]Let me type a name in the browser game[/-][+]Let me type and edit a name in the browser game[/+]treeform commentedon Sep 9, 2026
Fixed upstream by merged Windy #196 and Silky #69. Windy now delivers browser letters and Command-key/modifier events correctly. Silky automatically manages focused text entry and preserves fast shortcuts through its ordered input queue. The Silky web demo passed manual typing, replacement, focus, and keyboard-control checks, and the maintainer confirmed it works.
Closing this separate browser bug tracker as fixed upstream. Polyworld main and PR #9 still pin older dependencies; migration to Silky 0.2.0 and verification in the actual gallery remain tracked in #26 and PR #9.
The possible native input-method concern remains unverified and is recorded in #26. These changes do not claim to implement IME or clipboard fixes.