-
Notifications
You must be signed in to change notification settings - Fork 10
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(plugin-image): pixabay search vertical scroll bug on narrow screens #4223
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
📦 Next.js Bundle Analysis for @serlo/frontendThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
Page | Size (compressed) |
---|---|
global |
104.58 KB (🟡 +2 B) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Eight Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load |
---|---|---|
/___editor_preview |
529.67 KB (🟡 +136 B) |
634.25 KB |
/editor |
79.61 KB (🟡 +1 B) |
184.19 KB |
/entity/create/[type]/[taxonomyId] |
549.74 KB (🟡 +138 B) |
654.33 KB |
/entity/repository/add-revision/[...id] |
549.48 KB (🟡 +137 B) |
654.06 KB |
/page/create |
549.47 KB (🟡 +136 B) |
654.05 KB |
/taxonomy/term/create/[parent_id]/[id] |
549.22 KB (🟡 +137 B) |
653.8 KB |
/taxonomy/term/update/[id] |
549.16 KB (🟡 +137 B) |
653.75 KB |
/user/settings |
551.16 KB (🟡 +137 B) |
655.74 KB |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link
is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.
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.
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.
Top margin behaves a little weird. But not a big issue.
The important thing is the overlay is never cut off at the top any more. Thank you!
@elbotho It took a bit more changes than expected to achieve it, but the modal uses more height on narrow screens now. @LarsTheGlidingSquirrel If the modal's vertical positioning and usage of vertical space is what you meant by "Top margin behaves a little weird", that should be fixed now. |
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.
Thank you, way better now.
The actual fix is in the second commit.
In the first commit, I wanted to make it clear that the component doesn't only contain the button. Then after fixing the bug I thought it's also nice to split the big component.
Demo link (You will have to choose Pixabay and resize the screen)