[Bug] Typing into Raycast immediately after invoking it can leave an orphaned Pinyin candidate window and an unresponsive search field

Aperta
  • Qualcosa non va?
#140 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

@fanyange ci sta già lavorando.

Dal 3/11/2026.

  • #155 di @fanyange — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
swift
Ambito
desktop

Direzione di ricerca

Start by reading the Enhanced Mode floating-app detection and App Rules behavior described in the issue, then reproduce the steps with Raycast and Pinyin – Simplified. Compare the symptoms with #99 and PR #125, noting that the reported failure is in Raycast rather than the browser path. Done means the candidate window is dismissed or input switches before typing, and the search field remains responsive.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

On my machine, an App Rule forces ABC for Raycast, and Enhanced Mode is on. If I invoke Raycast while Pinyin – Simplified is active and start typing immediately, the Pinyin candidate window sometimes appears before Input Source Pro switches to ABC. After the switch, the candidate window stays on screen and the Raycast search field stops responding. This does not happen on every attempt.

Environment
  • macOS 27.0 (26A428), Apple Silicon
  • Input Source Pro 2.12.0 (707)
  • Raycast 2.4.1.0
  • Input source: macOS built-in Pinyin – Simplified (com.apple.inputmethod.SCIM.ITABC)
Relevant preferences
App Rule:                   com.raycast.macos -> com.apple.keylayout.ABC
Enhanced Mode:              on (Settings -> System); Accessibility permission granted
System-wide default source: unset
Keyboard restore strategy:  Use Default Keyboard Instead
Steps to reproduce
  1. Enable Enhanced Mode (Settings -> System) and grant Accessibility permission.
  2. In App Rules, set Raycast's input source to ABC.
  3. Switch the current input source to Pinyin – Simplified.
  4. Invoke Raycast (bound to ⌘Space on my machine) and immediately type a letter (e.g. n), without waiting for the launcher to settle.
  5. On some attempts, the Pinyin candidate window appears first, then Input Source Pro switches to ABC.
Expected

Either the input source switches before Raycast accepts input, or the active Pinyin composition is cancelled cleanly, so the search field receives subsequent keystrokes normally.

Actual

After this sequence, the candidate window stays on screen and the Raycast search field is stuck:

  • Enter does nothing.
  • Delete / Backspace does nothing to the search field.
  • The only recovery I found is to toggle the input source manually; the candidate window then disappears and the field responds again.
Image
Related
  • #99 describes the same visible symptoms (orphaned candidate window, Enter/Delete unresponsive) in the Chrome address bar. It is closed (2026-08-08); PR #125 / commit 09851ef makes the address bar rule fire on focus and only changes the browser path. This report concerns a different path, where the problem is still present in 2.12.0.
  • #67 describes 0.5–1 s input lag when typing immediately after invoking Raycast. That is a different symptom, included here for context.
  • #92 describes a Vivaldi/Chromium freeze lasting 15–30 s on macOS 26 due to an IMKInputSession deadlock. That is also a different symptom, included here for context.
Additional observations
  • Reproduction is intermittent; I have not measured a reliable rate.
  • Input Source Pro handles Raycast through Enhanced Mode's floating-app detection. With Enhanced Mode off, Raycast is not managed. This explains the setup step; I am not claiming it is the root cause.
Lingua principale
Swift
Stelle
3.6k
Fork
144
Merge medio
14h 21m
PR unite (30g)
7

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di runjuu/InputSourcePro

Tutte le issue di runjuu/InputSourcePro

Issue simili

Altre issue su Swift

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.