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

[BUG] Visbuilder toggle legend affordance doesn't work after initial toggle #6680

Closed
virajsanghvi opened this issue Apr 29, 2024 · 0 comments · Fixed by #6811
Closed

[BUG] Visbuilder toggle legend affordance doesn't work after initial toggle #6680

virajsanghvi opened this issue Apr 29, 2024 · 0 comments · Fixed by #6811
Labels
bug Something isn't working v2.15.0 vis builder

Comments

@virajsanghvi
Copy link

Describe the bug

Clicking on toggle legend affordance in visbuilder will work the first time, but not after that.

To Reproduce
Steps to reproduce the behavior:

  1. Create a new visualization with visbuilder
  2. Add fields to see a chart with a legend.
  3. Click on Toggle Legend affordance in bottom left hand corner of visual -> Should see legend state toggle
  4. Click on it again -> will toggle twice (if off, then on and then off) but effectively not work.

Expected behavior
Toggle Legend should toggle the legend off and on with each click.

OpenSearch Version
v 2.13.0 (not sure)

Dashboards Version
v 2.13.0

Plugins

Whatever's used in playground.

Screenshots

The affordance in the bottom right:
image

Host/Environment (please complete the following information):

  • OS: MacOS
  • Browser and version: Chrome 124.0.6367.92

Additional context

Add any other context about the problem here.

@virajsanghvi virajsanghvi added bug Something isn't working untriaged labels Apr 29, 2024
@kavilla kavilla linked a pull request May 24, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v2.15.0 vis builder
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants