Skip to content

πŸ‘―β€β™€οΈ fix: Dedupe @radix-ui/react-dismissable-layer to Unblock Body Clicks#74

Open
dustinhealy wants to merge 1 commit into
mainfrom
worktree-radix-dismissable-dedupe
Open

πŸ‘―β€β™€οΈ fix: Dedupe @radix-ui/react-dismissable-layer to Unblock Body Clicks#74
dustinhealy wants to merge 1 commit into
mainfrom
worktree-radix-dismissable-dedupe

Conversation

@dustinhealy

@dustinhealy dustinhealy commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Summary

Three copies of @radix-ui/react-dismissable-layer were getting installed (1.1.0 nested under react-tooltip, 1.1.1 hoisted via react-menu, 1.1.11 nested under the react-dialog 1.1.15 override). Each module copy holds its own DismissableLayerContext and originalBodyPointerEvents module variable, so when the sidebar Dropdown opens, the user clicks Settings, and the SettingsDialog mounts before the Dropdown portal has finished unmounting, the Dialog's copy snapshots document.body with the Dropdown's "none" still applied. When the Dialog later closes, its cleanup writes that stale "none" back onto the body and leaves the whole app unclickable until reload.

Pin a single shared version (1.1.11, the newest already pulled in by react-dialog 1.1.15) so all Radix packages route through one module copy with one shared layer context.

Change Type

  • Bug fix (non-breaking change which fixes an issue)

Testing

Confirmed behavior no longer present after using theme switcher, app buttons are now interactable again when closing settings dialog modal.

Checklist

  • My code adheres to this project's style guidelines
  • I have performed a self-review of my own code
  • I have commented in any complex areas of my code
  • My changes do not introduce new warnings
  • Local unit tests pass with my changes

Note

Low Risk
Dependency resolution-only change with no application code edits; risk is limited to Radix overlay/dismiss behavior across the pinned version.

Overview
Adds a package.json / bun.lock override pinning @radix-ui/react-dismissable-layer to 1.1.11, alongside the existing @radix-ui/react-dialog pin, so every Radix consumer resolves one copy of the dismissable-layer module.

That deduplication fixes a race where opening Settings from a sidebar dropdown while the dropdown portal is still tearing down left document.body with pointer-events: none after the settings dialog closed, because separate module copies each maintained their own body snapshot and cleanup.

Reviewed by Cursor Bugbot for commit 2a2c777. Bugbot is set up for automated code reviews on this repo. Configure here.

Three copies of @radix-ui/react-dismissable-layer were getting installed
(1.1.0 nested under react-tooltip, 1.1.1 hoisted via react-menu, 1.1.11
nested under the react-dialog 1.1.15 override). Each module copy holds
its own DismissableLayerContext and originalBodyPointerEvents module
variable, so when the sidebar Dropdown opens, the user clicks Settings,
and the SettingsDialog mounts before the Dropdown portal has finished
unmounting, the Dialog's copy snapshots document.body with the
Dropdown's "none" still applied. When the Dialog later closes, its
cleanup writes that stale "none" back onto the body and leaves the
whole app unclickable until reload.

Pin a single shared version (1.1.11, the newest already pulled in by
react-dialog 1.1.15) so all Radix packages route through one module
copy with one shared layer context.
@dustinhealy

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: 2a2c7777a5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with πŸ‘.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant