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

[Big Number with Trendline] Tooltip value is hidden #20531

Closed
2 of 3 tasks
ValentinC-BR opened this issue Jun 29, 2022 · 2 comments
Closed
2 of 3 tasks

[Big Number with Trendline] Tooltip value is hidden #20531

ValentinC-BR opened this issue Jun 29, 2022 · 2 comments
Labels
#bug Bug report

Comments

@ValentinC-BR
Copy link

There is a "cosmetic issue" on "Big Number With Trendline" charts.
We can't read the tooltip value anymore.

I labelled it as "Bug" as it is very painful and clearly affect our end-users (dashboard readers).

How to reproduce the bug

  1. Create a big number with trendline
  2. Add it to a dashboard
  3. Save the dashboard
  4. Hover on the line and try to read the value

Expected results

We should be able to read the line value.

Actual results

The value is hidden.

Screenshots

image

Environment

(please complete the following information):

  • browser type and version: Google Chrome Version 103.0.5060.53 (Official Build) (x86_64)
  • superset version: 1.5
  • python version: 3.9
  • node.js version: /
  • any feature flags active: /

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

The bug wasn't present in the earlier version of Superset (1.4 and before)

@ValentinC-BR ValentinC-BR added the #bug Bug report label Jun 29, 2022
@stephenLYZ
Copy link
Member

@ValentinC-BR Hi, this issue has been fixed by #20029. Please let me know if it makes sense and then we can close this one.

@ValentinC-BR
Copy link
Author

Is this bug fix included in the current 1.5 release ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

3 participants