_

@Aurion72 Yes, some big updates are coming soon. If there is a problem with versions `4.0.8` and `4.0.9`, they are likely regressions introduced to get around CSP violations surfaced by...

Thanks @CommanderRoot!

Thanks for the report. Looks like something here isn't working with IE11, in that `visibility: visible` isn't being applied. https://github.com/jlmakes/scrollreveal/blob/bc8fd853b56d06d265b2630ccb9c39e1db7fe9b7/src/instance/functions/style.js#L18-L30 Which at first glance suggests that `line 27`**`:`** `inlineMatch.some(m =>...

First-party support is coming in the next major release, but for now it looks like someone has authored a `@types/scrollreveal` package that looks pretty good. Give it a try! ```bash...

Thanks for this @PubliAlex. The short answer is yes, first-class support for this is coming. Since launch, ScrollReveal has boasted declarative reveal animations with as little as one line of...

Thanks for the report and reproduction @allaire I'm comparing changes in element state, and focusing on `{ revealed: false }` being set _after_ the element has revealed. `revealed = false`...

@simonkuran I actually don't remember where I landed on this. Using `option.afterReveal` to invoke `reveal()` is not exactly a use case well suited to ScrollReveal's design. This is one of...

Just to confirm, with `4.0.6` you ran into the same problem but with console errors?

@matthewattanasio Could you redeploy the site with `ScrollReveal` attached to the `window`? It'll help me debug if I can poke around its internal state (such as what elements ScrollReveal thinks...

Are you using the technique outlined in the [User Experience Guide](https://scrollrevealjs.org/guide/user-experience.html) to prevent flickering? As mentioned in the guide if you're using the `html.sr` selector as the base for your...