Repository navigation
fix(mac): caret tracking in ChatGPT and other Chromium shells (0.5.5) - #558
Merged
Merged
Conversation
ChatGPT (com.openai.codex) is a Chromium shell that refuses both accessibility switches, so its web content never reached the tree and typing there never moved the view. Reading the app element's role, subrole and description wakes it (bisected); Wind does that on attach and on every key press while zoomed. Its text has no character bounds, so the caret comes from the frames of the field's text runs, with trailing spaces counted, and a field whose caret misses one read keeps the last caret instead of jumping to the whole field. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SkyGaTQ1FTFz3Zwo4nohwd
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Zoomed in, typing in the ChatGPT desktop app never moved the view (owner report 2026-11-07).
Cause
com.openai.codex) is a custom Chromium shell (Codex Framework.framework), not stock Electron. It refusesAXManualAccessibility(-25205) andAXEnhancedUserInterface(-25208) on the app element, so its window holds six empty groups and Wind finds no text field.AXBoundsForRangeand the text-marker bounds return empty rects, but the field'sAXStaticTextruns do carry real frames.Fix (
CaretTracker.swift)Frameworks/* Helper (Renderer).appor a framework'sHelpers/), excluding browsers Wind already switches on.mac/docs/architecture.md(Caret following). Version 0.5.5.Verification
swift run wind-checks,e2e.py,e2e_mouse.py: all pass.e2e_caret.py: all pass exceptChrome: every key keeps the caret in view. That check fails identically on unmodifiedmain(first key compared against another Terminal's caret at x=371). It's pre-existing and environment-dependent, not from this change.Not covered
Mid-text and wrapped-line caret positions in ChatGPT are estimates (character share of the run).
🤖 Generated with Claude Code
https://claude.ai/code/session_01SkyGaTQ1FTFz3Zwo4nohwd