Mac browser smokes: headless Brave drops clicks in the bottom 80 px of a sandboxed frame (Archive, Chat emoji); use CI's Chromium

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript, playwright
领域
desktop, testing

调研方向

Start with scripts/archive-product-layout-smoke.mjs around line 502 and compare the failing real mouse click with the successful DOM click; the handler is in capsules/archive-manager/browser/archive-manager.js:70. Reproduce the smoke on Mac and CI Chromium, then determine whether the click loss is product behavior or a browser and test environment effect. Done when the cause is established and the Mac smoke behaves consistently.

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

描述

On this Mac (Chromium via the operator Playwright), scripts/archive-product-layout-smoke.mjs times out at line 502 on develop 30b166b05: a real mouse click on Extract selected leaves the status at "Select files to extract.", while a DOM click() starts the extract. The button is the element under its own centre point (elementFromPoint), so nothing visibly covers it. CI's test-capsules (Linux) passes the same smoke.

Probe output (develop tree, Cursor lane fix-jump-flash, lesson 1228):
CLICK_COMPARE {"before":{"status":"Select files to extract.","disabled":false,"rect":{"x":1028.25,"y":843.8125,"w":156.5,"h":30},"top":"BUTTON#extract-selected","same":true},"afterMouse":"Select files to extract.","afterDom":"Extracting selected files through Runtime..."}

The handler is capsules/archive-manager/browser/archive-manager.js:70. Open question: is this a product bug a Mac user would hit (the Archive tile is hidden in 2.0.0), or a Mac-only test-environment effect (scaling, a pointer event swallowed by a frame)? Either way the Mac pre-push product-ui-browser recipe fails on it.

主要语言
Rust
星标
6
派生
2
平均合并
1 天 3 小时
30 天内合并 PR
42

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

elastos/elastos-runtime 的其他 Issue

查看 elastos/elastos-runtime 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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