Skip to content

[bug]: Tooltip trigger throws errors when trigger content is plain text #5552

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task
myrta2302 opened this issue May 28, 2025 · 0 comments
Open
1 task
Labels
🐞 bug Something isn't working v9 v10

Comments

@myrta2302
Copy link
Contributor

myrta2302 commented May 28, 2025

🐞 Describe the bug

When using <post-tooltip-trigger> with only plain text as content the following errors occur:

  1. Uncaught TypeError: Cannot read properties of null (reading 'contextElement')
  2. Uncaught (in promise) TypeError: Cannot read properties of null (reading 'getBoundingClientRect')

🛠️ To Reproduce

Steps to reproduce the behavior:

  1. Use <post-tooltip-trigger> with text only e.g., <post-tooltip-trigger>Info</post-tooltip-trigger>.
  2. Hover on the tooltip.
  3. Observe console errors.

✨ Expected behavior

Suggestion (to discuss): It should check if the trigger contains only plain text (or no HTML element) and console.log an error.

Tasks

  • Check other triggers for plaintext errors and handle them in the same way as the tooltip
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working v9 v10
Projects
Status: 🆗 Ready
Development

No branches or pull requests

2 participants