Responsive Plugin will now respect steps to define max width #133
Conversation
This file contains 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
ghost
suggested changes
Feb 13, 2022
strausr
approved these changes
Feb 14, 2022
ghost
approved these changes
Feb 14, 2022
patrick-tolosa
deleted the
feature/adjust-default-behaviour-of-responsive-plugin
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull request for cloudinary/frontend-frameworks
For which package is this PR?
React, Angular
What does this PR solve?
This PR solves the default behavour of the responsive plugin.
Before this PR, the first render of the responsive plugin would render an image with the width of the parent container.
After this PR is merged, the responsive plugin will always respect the steps to define the width of the image on an initial render.
Final checklist