Skip to content
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.

Sign up for GitHub

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

Jump to bottom

consider a more specific selector for pointer-events #504

Closed
mreinstein opened this issue May 24, 2019 · 1 comment · Fixed by #511
Closed

consider a more specific selector for pointer-events #504

mreinstein opened this issue May 24, 2019 · 1 comment · Fixed by #511
Labels
🐛 bug

Comments

@mreinstein
Copy link
Contributor

mreinstein commented May 24, 2019 •
edited
Loading

This particular styling: https://github.com/atomiks/tippyjs/blob/master/src/scss/index.scss#L144-L146

What's happening for me is I have an tippy with html, interactive content. That content contains an SVG file. My svg file's <path> children are getting set to pointer-events: auto;.

Would it be easy to use a more specific selector so that this style won't be applied to my content?
@atomiks
Copy link
Owner

atomiks commented May 24, 2019

Yeah probably

.tippy-roundarrow > svg > path

@atomiks atomiks mentioned this issue May 29, 2019
Merged
atomiks added a commit that referenced this issue Jun 3, 2019
@atomiks
Use more specific selector for SVG arrow path (fix #504)
fe0dfb2
@atomiks atomiks mentioned this issue Jun 3, 2019
Merged
atomiks added a commit that referenced this issue Jun 3, 2019
@atomiks
Backport v5 fixes to v4 (#511)
dfcd8a3 
* Mounting + followCursor fixes (#509)

* Use more specific selector for SVG arrow path (fix #504)

* Ensure destroy()s unmounting is not impeded

* Fix interactive scrolling issue

* Ensure rAF is cancelled by hide()

* Distinguish the animationFrame variables
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐛 bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Backport v5 fixes to v4 atomiks/tippyjs
2 participants
@mreinstein @atomiks