Francis Champagne

Hey, the solutions above didn't work for me. Are there any updates on this?

You can find more info on the [Slate Configuration page](https://shopify.github.io/slate/docs/slate-configuration) ### Here's my working solution: ```js const PostcssCssnano = require("cssnano")() const PostcssAutoprefixer = require("autoprefixer")({ browsers: 'last 2 versions' }) const...

> Noticed the same a couple of days back - a temp fix would be to put a `position: fixed` on the wrapper. In case of the https://locomotive.ca/en would be...

This is a sign that LocomotiveScroll was initialized before the page was fully loaded. Basically, the height of the container is too small because it was computed, then some content...

@Mishkamshka lazyloading happens on the client-side. I don't know how the images are lazyloaded on your WordPress, but you would need to interact with the library that takes care of...

To me, this sounds like a CSS problem. You might have some margins that collapse in the container (which is the default). Try adding `display: flex;` to your container, it...

Hi, I currently have Locomotive Scroll working in Gatsby, I have some snippets down below. But I'm posting on here regarding the **`data-scroll-call`** and more specifically to **figure out how...

Hi @nzerk This sounds to me like you are missing the `location` callback. > The location is triggered on route change See [this file](https://github.com/fcisio/gatsby-locomotivescroll-starter/blob/master/src/components/layout.js) ```jsx const Layout = ({ children,...

@kkarkos In my experience, this is most likely due to an issue with a dependency. For me, I had the same issue, but it turned out that Emotion.js was the...

[Here's the solution](https://github.com/storybookjs/storybook/issues/12497#issuecomment-1272139961)