-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting a foreground blocks taps when scrolled #23
Comments
While the PR #24 does not fix it per se, it allows displaying headers that are supposed go with the scroll offset. |
@EyMaddis can I close this issue? I know, this is not a solution but looks like the good workaround |
Well, technically it is not solved, but a workaround is feasible (at least for me).
I am fine with closing as long as you don‘t have an idea how to properly fix this.
|
Maybe this can be properly solved by applying the foreground translation to the placeholder view or container instead of only the foreground. Unfortunately, I do not have time at the moment to look into this. |
Hi @EyMaddis, I just tried to reproduce your problem and it looks like everything works fine. The foreground wrappers have poinerEvents="box-none" prop, which means that touches won't work for this views, but will work for children. I think this problem can be solved in the client side app. What do you think about it? |
What do you mean? Client side meaning "by the user with renderPlaceholderView"? The wrapper has |
Yep
Will add this later. For now, I close this issue
|
Issue details
When setting a foreground an empty view is created that acts as a placeholder and wrapper.
This has
position: 'absolute'
and the height according to theparallaxHeight
property.Because of this, the empty view is always in front of everything that renders as the content of the ScrollView.
slightly scrolled and selected with the React-Native inspector:
Everything below the box is not touchable, i.e. the "Alle Anzeigen" button
Affected platforms
PR incoming
The text was updated successfully, but these errors were encountered: