apache/superset

Inconsistent Default Padding for Different Charts

Open

#31 033 ouverte le 22 nov. 2024

Voir sur GitHub
 (20 commentaires) (0 réactions) (1 assigné)TypeScript (72 837 stars) (17 291 forks)batch import
#bug:cosmeticcares:presetgood first issueviz:charts:barviz:charts:table

Description

Bug description

Depending on the type selected, the Superset UI will display charts with different alignments. Ideally they would be centered inside the card. Currently the padding differs on both sides leading to more whitespace on the left or right.

For Example:

  1. Go to Dashboard
  2. Click + Chart
  3. Select Table
  4. Click + Chart
  5. Select Bar Chart

Screenshots/recordings

Screenshot 2024-11-19 at 11 37 05 AM

Superset version

4.1.0

Python version

3.11

Node version

Not applicable

Browser

Chrome

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Guide contributeur

Stack technique
typescriptpythonhtmlcssreact
Domaine
frontenddesign
Type d'issue
bug
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-3 hours
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
blocked
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
clear
Prérequis
Basic CSSReact component stylingFamiliarity with Superset chart components
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
35
Direction de recherche
The padding inconsistency likely stems from CSS classes in the chart container components. Investigate the CSS files in the frontend/src/components directory, specifically any chart related components. Check if there are default padding styles applied differently per chart type. A fix would involve standardizing padding using a common CSS class or adjusting inline styles. The issue has 20 comments, some may contain hints about the root cause.