Intermittent findings and dynamic content: identity strength for repeated controls
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 39/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- playwright, testing-qa, typescript
- Área
- accessibility, devtools, testing
Línea de trabajo
The issue describes row-scoped control keys, a two-scan baseline stability pass, and operator guidance, but names no files or tests. Start by locating the baseline scanner, element-key generation, and documentation for data-dependent screens. Done means repeated controls retain separate identities, intermittent findings are marked, and operators have guidance; verify with the relevant scanner tests.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What
On a live application, collapsed identities for repeated controls (icon buttons per table row, kebab toggles per row) carry counts that track how many rows the page happens to show. The floor records those counts; runs against an unchanged codebase then see headroom or growth depending on live data.
Separately, a tooltip opened by the scanner's own keyboard walk was still in the DOM during its fade-out when axe ran and produced a new region finding on an unchanged page, one run in five. A bounded settle for transient popovers now runs between the walk and the providers.
Direction
- Stronger element keys for row-scoped controls (row identity plus control role) so identities do not collapse across rows.
- A stability pass at baseline that scans twice and records only findings present both times, marking the rest as intermittent.
- Guidance for operators on data-dependent screens.
- Lenguaje dominante
- TypeScript
- Estrellas
- 0
- Forks
- 0
- Merge medio
- 2 h 48 min
- PR fusionados (30 d)
- 8
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de usabl-dev/usabl
-
area: engine bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
Stop hook allows a stop on an unknown verdict, and the self-check prints IDLE for a null verdictAbiertoarea: assistants bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
area: engine bug security
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Overlay: browser context failures are counted per plugin, not per browser, and close is not sharedAbiertoarea: overlay bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
-
area: engine enhancement performance
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Todos los issues de usabl-dev/usabl
Issues similares
-
[Bug]: Circular app layout navigation and help icons are shifted upward in the official demoAbiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
cloudscape-design/components#5184 ·
Los mantenedores suelen responder en 2 días
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
JarX-Concepts/react-native-platform-components#130 ·
Los mantenedores suelen responder en 1 día
-
fix(api): optimize-for-web /preview outer catches miss asDecoderOutOfMemory on V8 OOM and SIGKILLAbiertoarea: backend bug priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
snapotter-hq/SnapOtter#3773 ·
Los mantenedores suelen responder en 1 día
-
ai-driven-qa ux-audit
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
linagora/twake-contacts-frontend#386 ·
Los mantenedores suelen responder en 1 día
-
git: README should state plainly that without --repository every reachable repository is in scopeAbiertodocumentation server-git v2
Dificultad 1/5 1-3 horas Aptitud para principiantes 84/100
modelcontextprotocol/servers#5225 ·
Los mantenedores suelen responder en 1 día