Blog Carousel Display

David Mesa Noack I actually found more on this issue (for me at least). I have the card carousel above the blog carousel. If I change the order of those so the card carousel is below the blog carousel it stops this issue. I'm unsure if you have the same setup.

Kyle King that's SO funny. I asked chatGPT and it said this: I did some digging into why changing the order of the modules seems to “fix” this issue, and it actually makes sense from a technical perspective. Both the Card Carousel and the Blog Carousel use Swiper.js, and the way Swiper initializes depends on when and how each instance is mounted in the DOM. When two Swiper instances are on the same page, they both try to measure their container dimensions during initialization. If the first carousel (for example, the Card Carousel) triggers layout changes such as transforms, overflows, or width adjustments while the second carousel (the Blog Carousel) is initializing, the second one can end up referencing the wrong element. That’s what causes the console error: Uncaught TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element' Basically, it’s a race condition between Swiper instances — whichever one initializes first affects how the next one computes its styles. By switching their order, you’re changing the initialization sequence so the Blog Carousel loads after the layout has stabilized, which prevents the error. This explains why the issue disappears when the Card Carousel is placed below the Blog Carousel. It’s not a real “fix” but rather a timing side effect. A more permanent solution would be for the module to ensure each Swiper instance initializes only after its container is fully rendered, or to trigger a swiper.update() once the page layout is complete.

David Mesa Noack that makes sense! I had given the supreme team a login for the site and they created a new page that didn't have the issue, so I copied the whole section to the page that did and boom, same thing! So I did a bit of testing and found that as the fix

Divi Supreme would it be possible to share the url privately?

Kyle King Of course, you can contact us at support@divisupreme.com and link to this issue so we can investigate further.

Divi Supreme chatGPT said this: I did some digging into why changing the order of the modules seems to “fix” this issue, and it actually makes sense from a technical perspective. Both the Card Carousel and the Blog Carousel use Swiper.js, and the way Swiper initializes depends on when and how each instance is mounted in the DOM. When two Swiper instances are on the same page, they both try to measure their container dimensions during initialization. If the first carousel (for example, the Card Carousel) triggers layout changes such as transforms, overflows, or width adjustments while the second carousel (the Blog Carousel) is initializing, the second one can end up referencing the wrong element. That’s what causes the console error: Uncaught TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element' Basically, it’s a race condition between Swiper instances — whichever one initializes first affects how the next one computes its styles. By switching their order, you’re changing the initialization sequence so the Blog Carousel loads after the layout has stabilized, which prevents the error. This explains why the issue disappears when the Card Carousel is placed below the Blog Carousel. It’s not a real “fix” but rather a timing side effect. A more permanent solution would be for the module to ensure each Swiper instance initializes only after its container is fully rendered, or to trigger a swiper.update() once the page layout is complete.