Skip to content

Fixed file browser covering the navigation - #3829

Merged
brandonpayton merged 4 commits into
WordPress:trunkfrom
dhruvang21:issue/3813
Jul 3, 2026
Merged

Fixed file browser covering the navigation#3829
brandonpayton merged 4 commits into
WordPress:trunkfrom
dhruvang21:issue/3813

Conversation

@dhruvang21

@dhruvang21 dhruvang21 commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Motivation for the change, related issues

Issue: #3813 - "File browser tab and settings panels can cover the Settings navigation tabs in the Site Manager"

Implementation details

Updated CSS

Testing Instructions (or ideally a Blueprint)

  1. Click the File browser tab
  2. Scroll the file browser content
  3. Confirm the Settings, File browser, Blueprint, Database, Logs navigation tabs remain visible and clickable at the top
  4. Switch between tabs navigation should never disappear behind content
@dhruvang21
dhruvang21 requested review from a team and ashfame June 24, 2026 13:38
Copilot AI review requested due to automatic review settings June 24, 2026 13:56

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review is ineligible. To be eligible to request a review, you need a paid Copilot license, or your organization must enable Copilot code review.

@brandonpayton

Copy link
Copy Markdown
Member

Hi @dhruvang21, thanks for submitting this PR! I grabbed your changes, and locally, I'm still seeing the issue. Would you be up for taking another look?

Screenshot 2026-06-26 at 3 23 01 PM
@dhruvang21

Copy link
Copy Markdown
Contributor Author

@brandonpayton I've fixed the issue in the latest commit.

fix-3813.mp4
Comment on lines +24 to +30
.tabPanelWrapper {
display: flex;
flex: 1 1 auto;
min-height: 0;
min-width: 0;
}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is this used anywhere? Can it be removed?

overflow-y: hidden;
-webkit-overflow-scrolling: touch;
position: relative;
z-index: 2;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do the z-index additions in this PR solve any problem? As far as I can tell, they aren't needed and can be removed.

-webkit-overflow-scrolling: touch;
position: relative;
z-index: 2;
background: #ffffff;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is this background setting needed?

@brandonpayton brandonpayton left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks for following up on this PR, @dhruvang21.

I took a look at the changes and made a lot of notes. A lot appears removable, and I left a suggestion for what may end up being the simplest fix here.

Would you be up for taking another look at this?

Comment on lines +36 to +39
position: relative;
isolation: isolate;
flex: 1 1 auto;
min-height: 0;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I tried removing these changes, and it didn't seem to make a difference for the fix. Can this be removed?

overflow-x: auto;
overflow-y: hidden;
-webkit-overflow-scrolling: touch;
position: relative;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is this solving any problem? I believe it can be removed without compromising the fix.

Comment on lines -34 to -35
overflow-x: auto;
overflow-y: hidden;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@dhruvang21 Based on my understanding and testing, this removal is what makes the tabs render properly again.

I think maybe we want to keep the overflow-x setting in order to allow horizontal scrolling the tabs when the settings pane is narrow enough to hide some of them.

I think it probably makes sense to restore these lines and add a flex-shrink: 0; here so the flexbox layout does not shrink the tabs container. That works to preserve both tab visibility and horizontal scrolling in my testing.

What do you think?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@brandonpayton yes, your approach is correct. I applied the changes you suggested by restoring the overflow-x styles and adding flex-shrink: 0; to the tabs container. It preserves horizontal scrolling when needed and fixes the tab rendering issue as expected.

I've pushed these changes in my latest commit. Could you please review it when you have a chance?

@brandonpayton brandonpayton left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This looks good. Let's ship it! Thanks, @dhruvang21!

@brandonpayton

Copy link
Copy Markdown
Member

Let's ship it!

Well... some CI tests are failing, but I think that's due to flakey tests. Let's rerun and confirm.

@brandonpayton
brandonpayton merged commit c4c5110 into WordPress:trunk Jul 3, 2026
53 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment