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

fix(horizontal filter bar filter labels): Increase max-width to 96px #25883

Merged
merged 6 commits into from
Nov 20, 2023

Conversation

rtexelm
Copy link
Contributor

@rtexelm rtexelm commented Nov 6, 2023

SUMMARY

Allow the size of the label to represent more of the filter title before truncation. Size changed from 60px to 96px

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

BEFORE:
Previous size of label

AFTER:
New size of label

TESTING INSTRUCTIONS

Create a filter with a title long enough to overflow 96px

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags: HORIZONTAL_FILTER_BAR
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@john-bodley
Copy link
Member

Thanks @rtexelm for the PR. Isn't the readability a function of screen size and thus should the maximum width be a relative (as opposed to absolute) measure?

@eschutho
Copy link
Member

eschutho commented Nov 7, 2023

/testenv up

Copy link
Contributor

github-actions bot commented Nov 7, 2023

@eschutho Ephemeral environment spinning up at http://54.185.241.142:8080. Credentials are admin/admin. Please allow several minutes for bootstrapping and startup.

@yousoph
Copy link
Member

yousoph commented Nov 8, 2023

/testenv up FEATURE_HORIZONTAL_FILTER_BAR= True

@rtexelm
Copy link
Contributor Author

rtexelm commented Nov 8, 2023

@john-bodley Yes I think it should be relative, however I determined that would be a more significant style change that might be better suited to a separate PR after consulting with the designers while this was in response to a particular request for it to be set to 96px

Copy link
Contributor

github-actions bot commented Nov 8, 2023

@yousoph Ephemeral environment spinning up at http://35.87.101.189:8080. Credentials are admin/admin. Please allow several minutes for bootstrapping and startup.

@eschutho
Copy link
Member

@kasiazjc, in light of @john-bodley's comment what do you think about us just removing the max-width on this element altogether. The filters do a pretty good job of adjusting their width on their own. Here's what it would look like with no max width on the label.

Screen.Recording.2023-11-16.at.5.54.35.PM.mov

@villebro
Copy link
Member

I tend to agree with @eschutho here. In my experience dashboard designers will usually tend to want the whole label to be visible, and if there's need for additional context that's not needed in the label, that can always be placed in the description to be displayed in the tooltip. So I vote for always showing the full label.

@kasiazjc
Copy link
Contributor

@kasiazjc, in light of @john-bodley's comment what do you think about us just removing the max-width on this element altogether. The filters do a pretty good job of adjusting their width on their own. Here's what it would look like with no max width on the label.

Screen.Recording.2023-11-16.at.5.54.35.PM.mov

I think removing max makes sense in this case, and good point @villebro about using description if needed. Let's do it :)

Copy link
Member

@eschutho eschutho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest to remove the max-width altogether

Co-authored-by: Elizabeth Thompson <eschutho@gmail.com>
Copy link

codecov bot commented Nov 17, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (d6fde3c) 69.00% compared to head (3396f4f) 69.00%.
Report is 48 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #25883      +/-   ##
==========================================
- Coverage   69.00%   69.00%   -0.01%     
==========================================
  Files        1938     1938              
  Lines       75831    75843      +12     
  Branches     8427     8427              
==========================================
+ Hits        52328    52332       +4     
- Misses      21334    21341       +7     
- Partials     2169     2170       +1     
Flag Coverage Δ
javascript 56.22% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@eschutho eschutho merged commit e7797b6 into apache:master Nov 20, 2023
30 checks passed
Copy link
Contributor

Ephemeral environment shutdown and build artifacts deleted.

@michael-s-molina michael-s-molina added the v3.0 Label added by the release manager to track PRs to be included in the 3.0 branch label Nov 21, 2023
michael-s-molina pushed a commit that referenced this pull request Dec 4, 2023
…25883)

Co-authored-by: Elizabeth Thompson <eschutho@gmail.com>
(cherry picked from commit e7797b6)
josedev-union pushed a commit to Ortege-xyz/studio that referenced this pull request Jan 22, 2024
cccs-rc pushed a commit to CybercentreCanada/superset that referenced this pull request Mar 6, 2024
@mistercrunch mistercrunch added 🍒 3.0.3 🍒 3.0.4 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 3.1.0 labels Mar 8, 2024
sfirke pushed a commit to sfirke/superset that referenced this pull request Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/XS v3.0 Label added by the release manager to track PRs to be included in the 3.0 branch 🍒 3.0.3 🍒 3.0.4 🚢 3.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants