Fix responsive behavior of SoSpecial carousel items across screen sizes #7307
+50
−48
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: DANIEL KATOTO <katotodan@gmail.com>
Contributor
|
🚀 Preview for commit f83e56c at: https://6952c83dfa81b7936b9b64b4--layer5.netlify.app |
Contributor
kishore08-07
left a comment
kishore08-07
left a comment
There was a problem hiding this comment.
Text is overlapping, Adjust the card width and layout for smaller screens to ensure proper content spacing.
Contributor
kishore08-07
left a comment
kishore08-07
left a comment
There was a problem hiding this comment.
@Katotodan
Use the Related Resources section on https://layer5.io/solutions/platform-engineering as the reference for the expected behavior.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes a rendering issue in the SoSpecial carousel where slider items were shrinking on small devices.
The root cause was related to Gatsby’s SSR behavior: the slider was initially rendered on the server without access to viewport-dependent values used in the slider settings (inside settings > responsive array), causing react-slick to compute incorrect dimensions.
To fix this, SSR rendering was kind of disabled for this specific component, and the slider settings are now adjusted programmatically on the client based on the current screen size. This ensures consistent and stable rendering across all breakpoints.
This PR fixes #7305
Here is the picture before
After
Notes for Reviewers
Signed commits