You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, saw your post on reddit and thought it might look promising so I took it for a test run. What I discovered, which also kinda makes sense, is that you are injecting section elements in order to create a place where you can do the intersection observer. Is that correct? if it is so, the it makes this really hard to use because I have my own section components that are styled and a bit of logic as well. which creates a situation with 2 sections back to back. Do you Think there would be a way to somehow provide our own custom section element with some required API, using ref with conjunction of useImperativeHandle to send the logic where needed.
The text was updated successfully, but these errors were encountered:
Hey, saw your post on reddit and thought it might look promising so I took it for a test run. What I discovered, which also kinda makes sense, is that you are injecting section elements in order to create a place where you can do the intersection observer. Is that correct? if it is so, the it makes this really hard to use because I have my own section components that are styled and a bit of logic as well. which creates a situation with 2 sections back to back. Do you Think there would be a way to somehow provide our own custom section element with some required API, using ref with conjunction of useImperativeHandle to send the logic where needed.
The text was updated successfully, but these errors were encountered: