-
Notifications
You must be signed in to change notification settings - Fork 63
Conversation
Storybook and Tailwind configuration previews: Ready Storybook: https://wordpress.github.io/openverse-frontend/_preview/2155 Please note that GitHub pages takes a little time to deploy newly pushed code, if the links above don't work or you see old versions, wait 5 minutes and try again. You can check the GitHub pages deployment action list to see the current status of the deployments. |
Size Change: -4.94 kB (-1%) Total Size: 892 kB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like an elegant solution. I think perhaps the default
layout would have been better suited as the "special" layout, and the default layout is the scrolling one, but of course I want to land this in time for our launch so we could consider that later. Thanks so much for getting to this quickly; LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to Zack's point but this PR works and fixes the problem.
8ff43f8
to
3b8dcf8
Compare
Fixes
Fixes #2150 by @obulat
Description
This is a better alternative to #2152 that uses @zackkrida's suggestion about splitting the height settings for "yellow" and "white" pages.
I previously thought that joining the layouts would give us two improvements:
However, I realized that since we used a
key
to make sure that the page is re-rendered to change the layout color, the number of re-renders would not change. Any change in color would cause the whole page to re-render.Also, the second point for setup is not as necessary. We might use the App.vue when we migrate to Nuxt 3 in future.
Having two different layouts (
default
for "yellow" full-height pages andcontentLayout
for the "white" scrollable pages) fixes the issues with header scrolling or the bottom of the footer being cut off.Testing Instructions
Checkout the PR and test that the height is correct on all pages, both on mobile and desktop, especially iOS.
Checklist
Update index.md
).main
) ora parent feature branch.
errors.
Developer Certificate of Origin
Developer Certificate of Origin