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

Partial-render residual: chrome mounts but content does not, so gaps.length==0 yields a false fixed

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
playwright, typescript
Área
accessibility, testing-qa

Línea de trabajo

Start by reading markUnseenScreens, runProviders, and the gate that builds cleanlyScannedScreens; the issue describes the reproduced case but names no file or test. Reproduce the partial render where chrome mounts and content does not, then weigh a deterministic content or control signal for flagging it unseen and adding a gap. Done means the affected screen cannot produce a false fixed verdict, without making results depend on timing or DOM order.

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

Descripción

area: engine bug

What this is

An accepted, documented residual of the #164 fix (no fixed on unscanned screens), filed so it
is visible rather than living only in a code comment. It is invariant-5 surface (a false green),
and it is a pre-existing weakness of gaps.length === 0 as a proxy for "this screen was measured."
#164 narrows the false-fixed population and does not widen it, so this is tracked, not a blocker.

The residual

cleanlyScannedScreens is built from scanned screens with gaps.length === 0. The gate treats
membership in that set as "the screen was genuinely measured this run," and only there does it mark
a disappeared floored identity fixed.

A screen whose chrome mounts but whose content region silently fails to mount defeats the proxy.
The keyboard walk lands on a real control, so isBodyOnly does not fire. No provider is denied or
throws, so runProviders records no gap. The affected content never renders, so its floored
identity is absent from the drafts. The screen therefore has zero gaps, enters
cleanlyScannedScreens, and the floored identity on the missing content is claimed fixed. That
is "absence of evidence read as evidence of absence," surviving at a narrower scope than before
#164.

Reproduced

Driven end to end through the real makeCheckRunner, makeConcreteStepRunner, markUnseenScreens,
and the gate during the #164 security review:

scan gaps: 0  stops: 1  drafts: 0
flagged unseen: []   gaps after unseen pass: 0
cleanlyScannedScreens: [ 'orders' ]
FALSE FIXED on partially-rendered screen: 1  [ 'orders/button-name' ]

Why it is not fixed in #164

The signal that would catch it, a genuine "content mounted" marker, is one the gate does not have.
markUnseenScreens detects only body-only blanks and duplicate renders; runProviders gaps only
on denied or thrown providers. A partial render with surviving chrome trips none of them. Closing
it needs a partial-render detector in markUnseenScreens, which is its own change, not a tweak to
the #164 guard.

Before #164 the gate marked fixed for any absent floored identity with no scan check at all, so a
completely unscanned floored screen got a false fixed. #164 excludes unscanned screens, gapped
screens, and body-only blanks. This partial-render case is the strict subset that remains.

Fix direction, if it is worth the cost

Add a partial-render detector to markUnseenScreens: a screen that reports a control count or a
content-region signal below a floor for its surface is flagged unseen and gets a gap, which removes
it from cleanlyScannedScreens. Whatever the detector, it must be deterministic, because a verdict
that depends on it must not depend on timing or DOM iteration order. This reintroduces some of the
per-application coupling the heuristics exist to avoid, so it is a tradeoff to weigh, not an obvious
win. This issue keeps it visible.

Origin

Found and reproduced in Chromium during the #164 security review. Accepted residual, not a blocker
for #164.

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

  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 usabl-dev/usabl

Todos los issues de usabl-dev/usabl

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.