I see the issue. The useScroll hook from Framer Motion requires the target container to have a non-static position. The container ref is on a div with relative, but we need to ensure the scroll offset is calculated correctly. Let me fix this by adding proper positioning to the container:

Wait, that's redundant since relative already sets position. The issue might be that Framer Motion's useScroll needs the container to use container option properly. Let me update the approach to use the window scroll instead of a container-based scroll:

Actually, the warning typically appears when a container is specified but doesn't have proper positioning. Let me revert that change and instead ensure we're not passing a container at all, which will default to window scroll tracking:

The warning from Framer Motion appears because it's checking if the container has a non-static position. The fix ensures the container div has an explicit position: relative style set via the style prop, which Framer Motion can reliably detect. This should resolve the scroll offset calculation warning while maintaining the same visual behavior of the scroll-based animation.