Incorrect calculation of nextOffsetY
@zombieJ 已经在做这个了。
开始于 2023年3月30日。
评估
这个 Issue 还没有评估数据。
描述
When recalculating nextOffsetY when popup goes beyond the viewport boundaries incorrect calculations occur.
I see problems in these lines:
https://github.com/react-component/trigger/blob/a73beef20376e3e32ecb918a0c1fbb0cdabb42f3/src/hooks/useAlign.ts#L313
https://github.com/react-component/trigger/blob/a73beef20376e3e32ecb918a0c1fbb0cdabb42f3/src/hooks/useAlign.ts#L327
Let's analyze each line separately.
nextOffsetX = targetAlignPointTL.x - popupAlignPointBR.x - popupOffsetX;
suppose
the target's bounding box is
{
width: 200px
left: 300px
right: 500px
}
the popup's bounding box is
{
width: 600px
left: 0px
right: 600px
}
first popup calculation without flip recalculation
{
width: 600px
left: 300px
right: 900px
}
x viewport border for example is 600px
Our popup climbs out of the border, so we implement the recalculation of nextOffsetX.
targetAlignPointTL.x = 300px
popupAlignPointBR.x = 600px
popupOffsetX = 0
nextOffsetX = 300px - 600px - 0 = -300px
Total we get that our popup left offset is -300px
and right 600px - 300px = 300px
And we observe approximately the following picture

In order to get the correct offset, you need to subtract the right coordinate of popup not from the left coordinate of the target, but from the right.
In other words, change targetAlignPointTL to targetAlignPointBR and get
nextOffsetX = targetAlignPointBR.x - popupAlignPointBR.x - popupOffsetX;
The situation is similar with Left to Right
nextOffsetX = targetAlignPointBR.x - popupAlignPointTL.x - popupOffsetX;
if we take fake data
target bb
{
width: 200px
left: 100px
right: 300px
}
popup bb
{
width: 500px
left: 0px
right: 500px
}
popup calculated bb
{
width: 500px
left: -200px
right: 300px
}
viewport left border 0px
popupOffsetX = 0px
then substituting into the current formula we get
nextOffsetX = 300px - 0px - 0px = 300px
Popup offset is 300px this is the right border of the target.
Why not just take the left offset of target and make it equal to nextOffsetX?
Well, or as a last resort, add the right border of the target to the existing offset
nextOffsetX = nextOffsetX + targetAlignPointBR.x = -200px + 300px = 100px
We will get the same 100px
In general, the problem is on the face and it brings a lot of inconvenience. Please pay attention to it!
- 主要语言
- TypeScript
- 星标
- 391
- 派生
- 245
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
react-component/trigger 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
react-component/trigger#593 · 1 个 reaction ·
-
难度 3/5 1-2 天 新手友好度 58/100
react-component/trigger#623 ·
-
难度 3/5 1-2 天 新手友好度 65/100
react-component/trigger#618 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 42/100
react-component/trigger#555 ·
-
难度 3/5 1-2 天 新手友好度 55/100
react-component/trigger#550 · 1 条评论 ·
查看 react-component/trigger 的全部 Issue
相似的 Issue
-
blocklist removal
难度 2/5 1-3 小时 新手友好度 65/100
MetaMask/eth-phishing-detect#296544 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
pastelsky/bundlephobia#1122 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100