Unable to trigger/hover `Tooltip` inside `PageCard` when `to` prop is present
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.1k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 57
Description
Environment
| Operating system | macOS 25.5.0 |
| CPU | Apple M4 Pro (12 cores) |
| Node.js version | v24.14.0 |
| nuxt/cli version | 3.37.0 |
| Package manager | pnpm@10.30.3 |
| Nuxt version | 4.4.8 |
| Nitro version | 2.13.4 |
| Builder | vite@7.3.6 |
| Config | compatibilityDate, css, devtools, i18n, icon, modules, nitro, ogImage, runtimeConfig, schemaOrg, site, sitemap, supabase, vite |
| Modules | @nuxt/eslint@1.16.0, @nuxt/ui@4.10.0, @nuxtjs/supabase@2.0.10, @nuxtjs/i18n@10.6.0, @vueuse/nuxt@14.4.0, @nuxtjs/seo@5.3.14, nuxt-gtag@5.0.0 |
Is this bug related to Nuxt or Vue?
Nuxt
Package
v4.x
Version
v4.1.10
Reproduction
Description
When to prop is present to PageCard the Tooltip used inside cannot be triggered on hover. When I inspect there is some kind of absolute positioned div on the PageCard probably that's blocking the hover.
Additional context
I don't know if it's a real issue worth paying attention but this is what I encountered. There could be some workarounds maybe hiding that div using :ui or triggering tooltip using some calculations but it could be nice if that just works.
Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked reproduction and inspect the rendered PageCard when its to prop is present, focusing on the element that blocks hover events. Compare the behavior with a PageCard without to and verify that the nested Tooltip can trigger on hover while navigation still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tailwindcss, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100