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

Abierto
  • ¿Algo no está bien?
#140 1 comentario 0 reacciones 0 asignados Ver en GitHub

@fanyange ya está trabajando en esto.

Desde el 3/11/2026.

  • #155 de @fanyange — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
swift
Área
desktop

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Swift
Estrellas
3.6k
Forks
144
Merge medio
14 h 21 min
PR fusionados (30 d)
7

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de runjuu/InputSourcePro

Todos los issues de runjuu/InputSourcePro

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.