When testing out different framework deployments, I stumbled on this.
It appears that the Gatsby deployment of my site displays the carousel component “expanded” on initial load. Then when interacted with, adjusts itself to display properly. This does not occur on the Next.js Deployment
Just thought I’d bring this to the teams attention. It’s not blocking any tasks I have at the moment, but im sure someone will come across this again soon
I checked both websites, and they look identical to me (without performing any interactions). Can you confirm that this is resolved on your end, and if so, what was the root cause?
Also, this could be related to a fix that we already pushed regarding carousel widths, so that might be why one of the deployed versions has no issues.
Unfortunately it is still appearing vertically on the Gatsby deployment for me, as the screenshot shows. I’m not exactly sure of the root cause either. Haven’t been able to fix it since the post
