-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Line chart tooltips broken on Firefox #7822
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
I am seeing the same here. This is due to #7102, more precisely the style for the body element in The My understanding of the change from the pull request above is that is meant to ensure that the body will always cover the entire window. A similar effect should be achievable with something like the following while avoiding the problem described above: html {
height: 100%;
}
body {
min-height: 100%;
display: flex;
flex-direction: column;
} |
@schoel-bis Are you sure this is the issue here? I've been investigating this same issue and am pretty sure the root cause is here: https://github.com/apache-superset/superset-ui-plugins/blob/master/packages/superset-ui-legacy-preset-chart-nvd3/src/NVD3Vis.js#L1081 We're removing all tooltips on the page whenever we rerender a chart, which is problematic especially on dashboards where multiple charts could have tooltips in the DOM. If your fix solves the issue here, than awesome, but I think there's another deeper problem that needs to be solved with the nvd3 chart plugin |
Well, frankly I wouldn't bet on this being the one and only problem with tooltips or NVD3 on Firefox or anywhere. Anyway, I wasn't seeing any tooltips whatsoever in Firefox and with that patch applied I have them back. |
@xtinec maybe you can confirm this as a side effect of your commit ? |
This bug was introduced by apache#7102 Using `position:absolute` on body gives `document.documentElement` a height of 0 which propagates to `clientHeight` on Firefox. This leads to a wrong calculation of the tooltip position in NVD3. The solution proposed here is to use `min-height: 100vh` instead of the current technique for stretching the body element to the full window height, thus keeping body and html together.
This bug was introduced by #7102 Using `position:absolute` on body gives `document.documentElement` a height of 0 which propagates to `clientHeight` on Firefox. This leads to a wrong calculation of the tooltip position in NVD3. The solution proposed here is to use `min-height: 100vh` instead of the current technique for stretching the body element to the full window height, thus keeping body and html together.
[Revert] Line chart tooltips broken on Firefox apache#7822
) (apache#7929)" This reverts commit 6df2a71.
@CoryChaplin This PR caused an issue: the standalone mode chart didn't show anymore. please see #8147 for details. We have reverted this PR from master branch. |
So, if the fix has been reverted, this needs to be re-opened, I suppose. I can't find how to do that, though. Although I do not currently have the time to investigate any further, I'd like to add a few observations:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
Could you open a more general issue or assign |
Hi, we are experiencing the same issue with latest stable release, I understand the fix was reverted? |
I'm having an issue like this, where hovering mouse over charts with firefox does not display any extra information. |
A clear and concise description of what the bug is.
Expected results
Hover point on the line, see a tooltip.
Actual results
No visible tooltip on Firefox (but it works on Chrome).
Screenshots
How to reproduce the bug
Environment
(please complete the following information):
Checklist
Make sure these boxes are checked before submitting your issue - thank you!
The text was updated successfully, but these errors were encountered: