Re-check why hover descriptions outside menus stay in the report's layer

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Read the comment in packages/pivotkit-react/src/popover.jsx around line 118 and docs/reference/theming.md at line 103, then review the timing evidence in #219. Check whether hover descriptions for the field list, zones, and chips can enter the top layer, and run the change in CI with the WebKit jobs rerun several times; done when those checks establish whether the earlier behavior was caused by the gap timing.

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

描述

area:react idea

packages/pivotkit-react/src/popover.jsx (comment at const [top] = useState(...), around line 118) and docs/reference/theming.md:103 say that in CI's WebKit on Linux a pointer moving from an "i" onto its description in the top layer closed it. #219 shows the WebKit/Linux runner moves the pointer in steps of about 280 ms, so the pointer rested in the 6 px gap longer than the 250 ms leave delay. The earlier observation was likely the same timing issue, not a top-layer one.

With #219 merged, check whether hover descriptions of the field list, zones and chips can go into the top layer like those in menus, with a CI run of that change and the WebKit jobs rerun several times. Not affected meanwhile: those descriptions work; they use --pk-layer-z stacking.

主要语言
JavaScript
星标
1
派生
1
平均合并
3 小时 21 分钟
30 天内合并 PR
250

环境准备

从这里开始

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

eizedev/pivotkit 的其他 Issue

查看 eizedev/pivotkit 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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