Matthew McVickar

I’m not sure if I’m misunderstanding the status of this issue, but is there a workaround for this currently, or does the jekyll-archives plugin need to be fixed?

After a lot of experimenting, I got this to work by changing my `import SnazzyInfoWindow from 'snazzy-info-window` to `const SnazzyInfoWindow = require('snazzy-info-window')` and moving it inside my `initMap()` function. Maybe...

@avechuche I think you need to switch the ES6 `import` function to another bundling method, like the `require()` I suggest above, which would be supported by RequireJS, Node.js, or Browserify.

@anthonysalamin I’m really not sure why it isn’t working. This CodePen setup is different than my setup (using Browserify and Babel), so I don't know how to debug it, but...

Aha, you had the same problem I did—and you fixed it! https://github.com/cferdinandi/bouncer/issues/37

I am also having this problem. I am having a difficult time reproducing it in CodePen, but in my local environment it is happening on pages where the content area...

I believe this is a duplicate of issue #1. There is [a workaround posted in that issue](https://github.com/metafizzy/flickity-fade/issues/1#issuecomment-486778382) as well as a PR (#11) awaiting review.

The cycle isn't a fixed width; you can set the container and the elements inside of it to any size you like in CSS. For a responsive design, you could,...

@joeworkman I played with this a bunch and discovered that you're right--the height issue is a hard one to get around. Since all of the elements in the cycle are...

This comment is a followup and context for [my comment on the WP Dev Blog post that mentions this change](https://make.wordpress.org/core/2024/06/24/miscellaneous-editor-changes-in-wordpress-6-6/#comment-46863), where I expressed confusion about this logic and its settings...