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

Bar charts HORIZONTAL margin adjustment error #26413

Closed
3 tasks done
kainchow opened this issue Jan 5, 2024 · 0 comments · Fixed by #26817
Closed
3 tasks done

Bar charts HORIZONTAL margin adjustment error #26413

kainchow opened this issue Jan 5, 2024 · 0 comments · Fixed by #26817
Assignees

Comments

@kainchow
Copy link
Contributor

kainchow commented Jan 5, 2024

When I create a bar chart and switch the Chart Orientation to HORIZONTAL, click on Show Legend and select the ORIENTATION of Legend as Left or Bottom, add a Margin for the legend, which is oriented Left and the Margin is adjusted to Bottom, and vice versa!

How to reproduce the bug

  1. Go to 'Create a Bar chart'
  2. Click on 'CUSTOMIZE-HORIZONTAL'
  3. Scroll down to 'Legend'
  4. Choose 'ORIENTATION-left/bottom'
  5. Enter the value in 'Margin'
  6. See error

Expected results

When left is selected for ORIENTATION, the margin is adjusted left, not bottom.

Actual results

When left is selected for ORIENTATION, the margin is adjusted to bottom, not left.

Screenshots

20240105-115417.mp4

Environment

(please complete the following information):

  • browser type and version: Microsoft Edge 120.0.2210.61
  • superset version: 3.1.0
  • python version: 3.9.18
  • node.js version: node -v
  • 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

Add any other context about the problem here.

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

Successfully merging a pull request may close this issue.

2 participants