Patrick Nelson

Ok, figured out download of additional assets (`trims`) and also better isolation of resources, ensuring it points to the local server instead of the CDN. Code wise, the last remaining...

Thanks for the update, didn't realize this was the case. I just tested this with my WebVR app and noticed that the frame rates dropped dramatically for some reason from...

This may be related to #87. I think it's a more fundamental issue relating to just not properly initializing it's position with a default mouse position (i.e. vertically in the...

Wow, I'm actually pretty surprised this has sat for so long... there are already PR's waiting to be merged to address this issue (details above and in issue #87) and...

It seems @stephband is "checked out" from this repository, if you will 😂 He's [alive and active on Twitter](https://twitter.com/stephband) but has decided to no longer pay attention to this repository,...

I've determined the root cause of this issue. This issue emerges from a general root/underlying issue associated with variable scoping and context. For example -- once the parallax finally reaches...

Also, by the way, I think making this more object-centric offers the opportunity to make the idling a bit more efficient, since I notice that once the target is reached...

See PR #92 which provides a fix for anyone out there seeing this issue.

I've actually simplified this further and refactored to `followPointer` by removing the need for a separate set of on/off frame animation functions. Now it's just one main function which then...

Well it's a combination of a few issues. Your CSS should have a graceful degradation to initialize at the proper position (if parallax itself never initializes), but also the parallax...