Skip to content

[6.x] Change how the slot with the "customize columns" works. Instead of an…#14885

Merged
jaygeorge merged 1 commit into
6.xfrom
change-fliter-listing-overflow-layout
Jun 26, 2026
Merged

[6.x] Change how the slot with the "customize columns" works. Instead of an…#14885
jaygeorge merged 1 commit into
6.xfrom
change-fliter-listing-overflow-layout

Conversation

@jaygeorge

Copy link
Copy Markdown
Contributor

Description of the Problem

Currently, the "Customize Columns" button is absolutely positioned to the right.
It's positioned absolutely in case there are many custom filters, which would otherwise push the "Customize Columns" button off screen, like in this example, where the numerous filters overflow underneath the control:

2026-06-26 at 12 56 15@2x

This is OK, but it's a fragile solution when we want to pin more buttons in the same space as "Customize columns".
I found that extra buttons now clash with the filter overflow, like this:

2026-06-26 at 12 59 24@2x

What this PR Does

Makes the layout less hacky by positioning the "Customize Columns" button within the parent flexbox layout

(After) you can see the filters now fade out as they overflow in the flexbox layout, rather than flowing underneath the buttons to the right

2026-06-26 at 13 01 33@2x

If we inspect the DOM we can now see the right icons are part of the parent flex layout, including a gap

2026-06-26 at 13 02 49@2x

How to Reproduce

  1. Go to a collection page
  2. Add a load of filters so they start to overflow below the Customize Columns button

… absolutely positioned element it now fits within the parent layout
@jaygeorge jaygeorge enabled auto-merge (squash) June 26, 2026 12:05
@jaygeorge jaygeorge merged commit 1c20231 into 6.x Jun 26, 2026
22 checks passed
@jaygeorge jaygeorge deleted the change-fliter-listing-overflow-layout branch June 26, 2026 12:13
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 this pull request may close these issues.

1 participant