Skip to content

chore: improve scroll behavior of DashboardLayout wrapped pages #19396

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

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

brettkolodny
Copy link
Contributor

@brettkolodny brettkolodny commented Aug 18, 2025

Updates the the DashboardLayout to create a singular scroll area between the top nav bar and the deployment banner on the bottom. Also improves the scroll behavior of the org settings pages.

CleanShot 2025-08-18 at 13 53 01
CleanShot.2025-08-18.at.13.49.29.mp4

@brettkolodny brettkolodny changed the title chore: improve scroll behavior of DashboardLayout wraped pages chore: improve scroll behavior of DashboardLayout wrapped pages Aug 18, 2025
@brettkolodny brettkolodny marked this pull request as ready for review August 18, 2025 18:43
@brettkolodny brettkolodny requested a review from aslilac as a code owner August 18, 2025 18:43
@brettkolodny brettkolodny marked this pull request as draft August 18, 2025 18:43
@brettkolodny brettkolodny marked this pull request as ready for review August 18, 2025 19:00
Copy link
Member

@aslilac aslilac left a comment

Choose a reason for hiding this comment

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

lgtm! this is a precarious enough change I'd like to get a second pair of eyes on it tho, maybe @Parkreiner?

@brettkolodny
Copy link
Contributor Author

Agreed, and if someone has time to pull this down and check it out locally I'd appreciate it too. A weak point of our storybook setup is we don't really test for scrolling content as often as we should

@aslilac
Copy link
Member

aslilac commented Aug 18, 2025

I ran it locally and didn't notice any jank, I'm just paranoid lol

Copy link
Member

@Parkreiner Parkreiner 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! I tested as many pages as I could, both with and without the bottom bar, and things seemed to work well

Just had some small nits on the styling

@@ -76,7 +76,7 @@ const GroupsPage: FC = () => {
}

return (
<>
<div className="w-full max-w-screen-2xl pb-10">
Copy link
Member

Choose a reason for hiding this comment

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

Is there any way we can refactor the layouts to bake the pb-10 in by default? I'm worried that it could get missed as we add new page types in the future

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I believe I tried doing that, but the pages aren't set up consistently so it didn't end up being feasible. And making the pages more consistent seemed out of scope for this PR

@@ -108,7 +108,7 @@ export const TemplateLayout: FC<PropsWithChildren> = ({

if (error || workspacePermissionsQuery.error) {
return (
<div css={{ margin: 16 }}>
<div className="m-4">
Copy link
Member

Choose a reason for hiding this comment

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

Totally okay if this isn't feasible because it would require too many changes elsewhere, but could we update this to use padding instead? I feel like margins are an anti-pattern ~95% of the time

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.

3 participants