Open RobSchilderr opened 1 year ago
Thanks for reporting this, we are checking your inquiry with the team and will update you soon with our insights.
Hi @RobSchilderr, A new version with a fix to the order of the plugins was just released, and now the example in the docs should work as expected. Please let me know if you still experiencing issues
New issue for cloudinary/frontend-frameworks
"@cloudinary/react": "^1.11.0",
For which package is this issue?
"@cloudinary/react": "^1.11.0",
Describe the issue in a sentence or two.
The AdvancedImage component's responsiveness is compromised when used with conflicting plugins simultaneously, which can cause excessive data download for users. A simplified implementation that only utilizes the responsive plugin resolves the issue. This issue may be a bug in the React SDK.
Issue Type (Can be multiple)
Steps to reproduce
Error screenshots
N/A
Browsers (if issue relates to UI, else ignore)
Versions and Libraries (fill in the version numbers)
package SDK version
Config Files (Please paste the following files if possible)
Package.json:
Code Examples
Original implementation:
Simplified implementation:
In the original implementation, the AdvancedImage component is used with three plugins: the placeholder plugin with a blur mode (if withBlur is true), the lazyload plugin, and the responsive plugin with 150 steps. In contrast, the simplified implementation only uses the responsive plugin with 150 steps and sets the loading attribute to "lazy". This results in a more efficient and responsive image-loading experience for users.