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

Carry provider keyboard observations through snapshot acquisition

未关闭
#3,529 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@thymikee 已经在做这个了。

开始于 2026年10月13日。

  • #3593 来自 @thymikee —— 未关闭

评估

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

调研方向

Start with packages/kernel/src/snapshot.ts:325 and packages/contracts/src/ios-snapshot.ts:150, then trace provider adapters and the keyboard-occlusion goldens and provider-carriage tests. Decide the provenance vocabulary and how much the tap-occlusion guard trusts derived bands before implementation. Done means observations reach response-level publication, the goldens and carriage tests are extended, and live checks cover iOS providers, Android Appium, and floating keyboards.

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

描述

enhancement ready-for-agent

Purpose

Keyboard facts promise measured bands or proven absence (packages/kernel/src/snapshot.ts:325), but the iOS provider acquisition carrier has no keyboard field (packages/contracts/src/ios-snapshot.ts:150). On Appium and limrun iOS, consumers fall back to scanning the tree for keyboard nodes (tester-army/e2e surface.ts:153-156). Limrun Android already delegates to ADB.

Required behavior

  • Provider acquisition carriers and adapters carry keyboard observations to response-level publication.
  • Distinguish visibility-only probes, measured frames, derived frames, and unknown. Missing keyboard nodes cannot prove absence.
  • Tree-derived evidence needs an explicit contract extension.

Open decisions (needed before implementation)

  • Provenance vocabulary.
  • How far the tap-occlusion guard trusts derived bands.

Completion

Extend the keyboard-occlusion goldens and provider-carriage tests. Live: iOS providers and Android Appium, including floating keyboards.

主要语言
TypeScript
星标
5k
派生
334
平均合并
11 小时 48 分钟
30 天内合并 PR
605

环境准备

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

从这里开始

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

callstack/agent-device 的其他 Issue

查看 callstack/agent-device 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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