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

iOS alert resolution reads every element of the app window when a popover is found

Abierto
  • ¿Algo no está bien?
#2,905 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
64/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
swift
Área
mobile-dev, performance, testing-qa

Línea de trabajo

Start in RunnerTests+Alert.swift around the resolution root and preferredAlertTitle, then inspect actionableElements in RunnerTests+SystemModal.swift and compare the no-alert fix from #2901. Bound the XCTest queries under the popover or dimming region and check the deadline between reads. Add a popover-over-long-list regression fixture and verify the command finishes within its budget.

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

Descripción

ready-for-agent

Problem

Alert handling in the iOS runner reads per element over a whole app window, with no deadline check, when a popover is found. #2901 fixed the no-alert case (firstDismissPopupWindow now uses one predicate query). The same cost remains when a popover is present:

  • the resolution root becomes the whole app window (RunnerTests+Alert.swift ~47-48);
  • actionableElements (RunnerTests+SystemModal.swift ~121-143) makes about 5 XCTest reads for each button, cell and link;
  • preferredAlertTitle (RunnerTests+Alert.swift ~219) walks every descendant.

A popover over a list with many rows can therefore overrun the command watchdog and keep the runner busy. The synchronous XCTest work continues after the watchdog answers the client, so later commands get RUNNER_BUSY. This is the same wedge #2901 fixed for the no-alert path.

Required behavior

Alert resolution makes a bounded number of XCTest reads, whatever the screen size: query under the dimming or popover region, use predicates instead of walks, and check the command deadline between reads. Add a regression fixture with a popover over a long list, and assert the command finishes well within its budget.

Found in the adversarial review of #2901.

Lenguaje dominante
TypeScript
Estrellas
5.1k
Forks
339
Merge medio
12 h 53 min
PR fusionados (30 d)
644

Preparar el entorno

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 callstack/agent-device

Todos los issues de callstack/agent-device

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.