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: Filters alert width #24801

Merged

Conversation

michael-s-molina
Copy link
Member

SUMMARY

Fixes the filters alert width and also changes the modal width.

Following @kasiazjc's comment in #24559:

I think in general we have to bump the width of the modal in the default mode to ~880px (and resize just after it not longer fits in the screen), so that everything is more visible.

I adjusted the modal to have a fixed base width instead of percent based one. I set it to 1000px instead of 880px as a middle ground.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Screenshot 2023-07-25 at 11 36 58 Screenshot 2023-07-25 at 11 46 35

TESTING INSTRUCTIONS

Make sure the the width of the filters' alert takes the available space.

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • 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

@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 Jul 25, 2023
@codecov
Copy link

codecov bot commented Jul 25, 2023

Codecov Report

Merging #24801 (af1a018) into master (4a81284) will increase coverage by 0.00%.
Report is 5 commits behind head on master.
The diff coverage is 50.00%.

❗ Current head af1a018 differs from pull request most recent head b1b7719. Consider uploading reports for the commit b1b7719 to get more accurate results

@@           Coverage Diff           @@
##           master   #24801   +/-   ##
=======================================
  Coverage   68.95%   68.96%           
=======================================
  Files        1902     1902           
  Lines       73998    73999    +1     
  Branches     8195     8195           
=======================================
+ Hits        51029    51030    +1     
  Misses      20850    20850           
  Partials     2119     2119           
Flag Coverage Δ
javascript 55.79% <50.00%> (+<0.01%) ⬆️

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

Files Changed Coverage Δ
...tersConfigModal/Footer/CancelConfirmationAlert.tsx 100.00% <ø> (ø)
...eFilters/FiltersConfigModal/FiltersConfigModal.tsx 71.09% <50.00%> (+0.13%) ⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

Copy link
Member

@justinpark justinpark left a comment

Choose a reason for hiding this comment

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

Looks good to me other than 1000px adjustment change (will be reviewed @kasiazjc

@kasiazjc
Copy link
Contributor

SUMMARY

Fixes the filters alert width and also changes the modal width.

Following @kasiazjc's comment in #24559:

I think in general we have to bump the width of the modal in the default mode to ~880px (and resize just after it not longer fits in the screen), so that everything is more visible.

I adjusted the modal to have a fixed base width instead of percent based one. I set it to 1000px instead of 880px as a middle ground.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Screenshot 2023-07-25 at 11 36 58 Screenshot 2023-07-25 at 11 46 35

TESTING INSTRUCTIONS

Make sure the the width of the filters' alert takes the available space.

ADDITIONAL INFORMATION

  • Has associated issue:

  • Required feature flags:

  • 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

I think on the smaller screens, modals that are that big of a size can be overwhelming (that's why I would prefer to avoid them) and I do not think that we add that much value with the increased size (especially because with 880x the fields are already bigger than our default + 240px seems like enough). I think we use width of 880px we use in the dashboard properties etc and the 1000px+ is used for alerts&reports as there is a lot of content and different inputs etc.

Can be convinced that 1000px is better though if you give me reasons @michael-s-molina :D

@michael-s-molina
Copy link
Member Author

Can be convinced that 1000px is better though if you give me reasons @michael-s-molina :D

I was worried it wouldn't work for Airbnb but I checked with @justinpark and 880px is fine for most cases. I changed the width back to 880px.

@kasiazjc
Copy link
Contributor

Can be convinced that 1000px is better though if you give me reasons @michael-s-molina :D

I was worried it wouldn't work for Airbnb but I checked with @justinpark and 880px is fine for most cases. I changed the width back to 880px.

Thank you @michael-s-molina ❤️

Copy link
Contributor

@kasiazjc kasiazjc left a comment

Choose a reason for hiding this comment

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

LGTM ✨

@michael-s-molina michael-s-molina merged commit 4b1f1d4 into apache:master Jul 26, 2023
26 checks passed
michael-s-molina added a commit that referenced this pull request Jul 26, 2023
(cherry picked from commit 4b1f1d4)
@mistercrunch mistercrunch added 🍒 3.0.0 🍒 3.0.1 🍒 3.0.2 🍒 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
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.0 🍒 3.0.1 🍒 3.0.2 🍒 3.0.3 🍒 3.0.4 🚢 3.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants