-
-
Notifications
You must be signed in to change notification settings - Fork 520
Description
Describe the bug
I have a very large application that is using various floating shadcn-svelte components eg. drop downs, pop overs, tooltips etc. I often find that they become 'stuck' as in they stop working and won't display and even stop navigation of the rest of the application. I have to force a page reload to get them working again. i've noticed that sometimes these styles get stuck and don't get removed. Any idea why this is happening ? Do you have an recommendations how I should be using these components to stop this happening ? Maybe its how I've implemented them ?
Any suggestions or help would be greatly appreciated before closing this issue for not having a REPL :D
Reproduction
I can't reproduce this issue in a REPL as its part of a massive application with tooltips, dropdowns, and select boxes through out. It is most likely something to do with how these have been implemented. Some advice on best practices so this doesn't happen would be greatly appreciated.
Logs
System Info
System:
OS: macOS 15.6.1
CPU: (12) arm64 Apple M2 Max
Memory: 100.59 MB / 32.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 24.5.0 - /Users/[REDACTED]/Library/pnpm/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 11.5.1 - /Users/[REDACTED]/Library/pnpm/npm
pnpm: 10.20.0 - /Users/[REDACTED]/.nvm/versions/node/v23.1.0/bin/pnpm
bun: 1.3.0 - /Users/[REDACTED]/.bun/bin/bun
Browsers:
Brave Browser: 143.1.85.120
Chrome: 143.0.7499.193
Firefox: 145.0.2
Safari: 18.6
npmPackages:
@lucide/svelte: ^0.539.0 => 0.539.0
@sveltejs/kit: ^2.43.7 => 2.48.4
bits-ui: ^2.14.2 => 2.14.2
mode-watcher: ^1.1.0 => 1.1.0
svelte: ^5.43.2 => 5.43.2
svelte-sonner: ^1.0.5 => 1.0.5
tailwindcss: ^4.0.0 => 4.1.16Severity
blocking all usage of shadcn-svelte