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.

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

[Feature] 指定Tooltip的父节点 #18435

Closed
viking7982 opened this issue Mar 28, 2023 · 1 comment · Fixed by #18436
Closed

[Feature] 指定Tooltip的父节点 #18435

viking7982 opened this issue Mar 28, 2023 · 1 comment · Fixed by #18436

Comments

@viking7982
Copy link
Contributor

What problem does this feature solve?

echarts的父组件设置了overflow:hidden,所以tooltips需要插入到父组件的外面。

虽然现在支持了body插入,但是我们业务的滚动元素不是body,所以插入到body也不能满足需求。

因此希望可以指定插入的DOM节点。

What does the proposed API look like?

tooltip.getAppendElement: e => e.closest('.scroll-container')

@echarts-bot echarts-bot bot added the pending We are not sure about whether this is a bug/new feature. label Mar 28, 2023
@echarts-bot
Copy link

echarts-bot bot commented Mar 28, 2023

@viking7982 It seems you are not using English, I've helped translate the content automatically. To make your issue understood by more people and get helped, we'd like to suggest using English next time. 🤗

TRANSLATED

TITLE

[Feature] Specifies the parent node of the Tooltip

BODY

What problem does this feature solve?

The parent component of echarts has overflow:hidden set, so tooltips need to be inserted outside the parent component.

Although body insertion is now supported, the scrolling element of our business is not the body, so inserting it into the body cannot meet the requirements.

Therefore, it is hoped that the inserted DOM node can be specified.

What does the proposed API look like?

tooltip.getAppendElement: e => e.closest('.scroll-container')

@Ovilia Ovilia added topic: tooltip and removed pending We are not sure about whether this is a bug/new feature. labels Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants