Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Secure Keyboard Entry refusal should name the app/window that enabled it

Abierto
  • ¿Algo no está bien?
#176 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
67/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
macos, swift
Área
accessibility, desktop

Línea de trabajo

Start from the typing route that refuses input when Secure Keyboard Entry is active, then check how desktop_apps reports session.secure_keyboard_entry and how focus information is exposed. Include the focused app identity in the refusal so the user can identify the blocking dialog; done when the refusal names the app holding focus or provides its bundle ID.

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

Descripción

What happened

Typing into an ordinary web form field in Safari was refused:

desktop_insert → refused
"Secure keyboard entry is on, as for a password field or a terminal's
 Secure Keyboard Entry, so typed text can't be delivered. Nothing was typed."
hint: "Use a field that isn't secure, or turn off Secure Keyboard Entry in the app."

There was no secure field anywhere near the target. The actual cause was a
com.apple.NetAuthAgent SMB password dialog open behind the Safari window,
holding focus on an AXSecureTextField. macOS enables secure input globally
while that field has focus, so every synthesized keystroke in every app is
blocked.

Why the current hint doesn't help

"turn off Secure Keyboard Entry in the app" is ambiguous — which app? The
agent is pointed at its own target window, which is not the cause. I only
found the real cause by noticing focus.bundle_id had changed to
com.apple.NetAuthAgent in an unrelated desktop_apps call, then inspecting
that window.

Also note the fix is something the agent cannot do: system password prompts
are (correctly) refused to agents, so the only resolution is asking the user
to dismiss a specific dialog — which requires naming it.

Suggestion

desktop_apps already reports session.secure_keyboard_entry. When a typing
route is refused for this reason, include the app that currently holds focus
in the refusal, e.g.:

"Secure keyboard entry is on. com.apple.NetAuthAgent ("Enter your name and
 password for the server …") holds focus on a secure field. Ask the user to
 dismiss or complete it; agents cannot answer system password prompts."

Even just focused_bundle_id in the error payload would be enough to let the
agent inspect and describe it.

Environment

Desktop Tools 0.16.1 (app + MCP), macOS 27, Safari 27

Lenguaje dominante
Swift
Estrellas
0
Forks
0
Merge medio
39 min
PR fusionados (30 d)
144

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 githubnext/desktop-tools

Todos los issues de githubnext/desktop-tools

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.