Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
  • 哪里不对？
#186 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@eparenti 已经在做这个了。

开始于 2026年10月26日。

  • #313 来自 @eparenti —— 未关闭

评估

难度
5/5
预计耗时
一周以上
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
playwright, typescript
领域
accessibility, testing-qa

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
0
派生
0
平均合并
1 小时 22 分钟
30 天内合并 PR
19

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

usabl-dev/usabl 的其他 Issue

查看 usabl-dev/usabl 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。