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

Data not aligned (bad choice of font) #14060

Closed
squalou opened this issue Apr 9, 2021 · 10 comments
Closed

Data not aligned (bad choice of font) #14060

squalou opened this issue Apr 9, 2021 · 10 comments
Labels
explore:design Related to the Explore UI/UX good first issue Good first issues for new contributors viz:charts:table Related to the Table chart

Comments

@squalou
Copy link
Contributor

squalou commented Apr 9, 2021

Screenshot

Using Superset 1.0.1

Here for dates fields :

image

Here for some prices

image

Description

When analysing data in a table, one expects them to be nicely aligned.

It's especially the case regarding money amounts.

Fonts should be monospace.

@zhaoyongjie zhaoyongjie added explore:design Related to the Explore UI/UX viz:charts:table Related to the Table chart good first issue Good first issues for new contributors labels Apr 12, 2021
@mohansaimandalapu
Copy link

mohansaimandalapu commented Apr 12, 2021

Hi squalou

I am interested in solving this issue, this is my first PR, can you explain how to solve this issue. Thank you

@squalou
Copy link
Contributor Author

squalou commented Apr 12, 2021

I did an ugly fix on my side, and it's probably NOT the way to go, nevertheless here's what I did.

in file superset-frontend/stylesheets/less/variables.less I removed 'Inter' font entirely

< @font-family-sans-serif: 'Inter', Helvetica, Arial;
---
> @font-family-sans-serif: Helvetica, Arial;

it works but ... it has effects everywhere. (which is fine on my setup)

@squalou
Copy link
Contributor Author

squalou commented May 26, 2021

Are there any update ?
I'm testing 1.2.0-rc2 with my patch, would be glad to get rid of it.

@rajpratyush
Copy link

can i take this issue up?

@stale
Copy link

stale bot commented Apr 30, 2022

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 .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Apr 30, 2022
@rusackas
Copy link
Member

@geido I think you took a look at this quite some time ago using the monospaced variant of Inter. Do you remember where that landed? I seem to recall the difficulty being around knowing/mapping which columns to which we should apply the styling/class

@stale stale bot removed the inactive Inactive for >= 30 days label Jan 17, 2023
@geido
Copy link
Member

geido commented Jan 18, 2023

@rusackas the fix was applied to the table in this PR #19668. There's probably more work to do to make sure this works fine everywhere but as far as I remember it should look good now in most places.

@rusackas
Copy link
Member

Ok, closing this for now then... @squalou please feel free to open a fresh issue with updated specifics if we need to investigate this further! Thank you!

@squalou
Copy link
Contributor Author

squalou commented Jan 18, 2023

Great news of sort :)
Is there an easy way to know in which release this PR has landed ? (if it has already).

I remember trying 2.0.1-rc1 last October, it was not yet right.

@squalou
Copy link
Contributor Author

squalou commented Jan 19, 2023

I'll sadly have to open a fresh issue,
here is a 2.0.1 table with dates

2023-01-19_11-2superset-2 0 2-misaligned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
explore:design Related to the Explore UI/UX good first issue Good first issues for new contributors viz:charts:table Related to the Table chart
Projects
None yet
Development

No branches or pull requests

6 participants