palantir/blueprint

[v5] Popover not closing when navigating lazily loaded pages via React Router

Open

#6,518 建立於 2023年11月6日

在 GitHub 查看
 (2 留言) (3 反應) (0 負責人)TypeScript (20,263 star) (2,167 fork)batch import
P2Package: coreType: bughelp wanted

描述

Environment

  • Package version(s): @blueprintjs/core 5.6.0
  • Operating System: Windows 10
  • Browser name and version: Chrome 118

Code Sandbox

https://codesandbox.io/p/sandbox/blueprint5-popover-issue-9zjj9x

Steps to reproduce

  1. Use the navbar menu to navigate to "Page 2"

Actual behavior

When using React Router to navigate to a lazily loaded page, the popover menu does not close and loses interactivity.

Expected behavior

The popover menu should close after the page transition.

Possible solution

No current solution to propose. We're currently migrating our code from Blueprint v4 to v5 and noticed this issue.

貢獻者指南

技術棧
typescriptreactcss
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
ReactReact RouterBlueprint v5
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Investigate the Popover component's close behavior in the context of React Router navigation with lazy loaded pages. Review the CodeSandbox provided to replicate the issue. Check the Popover's event handling and see if the component unmounts or state changes during navigation. Look for any existing discussions or related issues in the Blueprint repository about popover closing. Possible fix involves ensuring the popover closes when the route changes, perhaps by listening to navigation events or using a key prop.