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
Wrapping a <ViewOverflow> predecessor with <TouchableOpacity> or applying styles to it overrides the overflow.
First thing's first - Thanks for this module.
so...
expected behavior: <ViewOverflow> predecessors will overflow properly, pressing will invoke opacity change on entire <View>
actual behavior: <ViewOverflow> is being clipped, pressing invokes opacity change on entire <View>
Seems the case is a <ViewOverflow> predecessor which is an ancestor of the actual overflowed element. You can see in the images that styling the actual overflowed element doesn't produce the problem.
I'm new to RN, wanted to submit a PR but felt pretty clueless.
Applying styles reproduces the problem. (I've test backgroundColor, opacity, border)
Looks like this is related. (It seems safe to guess that <TouchableOpacity> applies opacity)
Wrapping a
<ViewOverflow>
predecessor with<TouchableOpacity>
or applying styles to it overrides the overflow.First thing's first - Thanks for this module.
so...
<ViewOverflow>
predecessors will overflow properly, pressing will invoke opacity change on entire<View>
<ViewOverflow>
is being clipped, pressing invokes opacity change on entire<View>
Seems the case is a
<ViewOverflow>
predecessor which is an ancestor of the actual overflowed element. You can see in the images that styling the actual overflowed element doesn't produce the problem.I'm new to RN, wanted to submit a PR but felt pretty clueless.
basic code:
output:
Applying
<TouchableOpacity>
on<IconIndicator>
:output:
Styling:
Applying styles reproduces the problem. (I've test
backgroundColor
,opacity
,border
)Looks like this is related. (It seems safe to guess that
<TouchableOpacity>
appliesopacity
)output:
Applying
style: { backgroundColor: 'yellow' }
:Applying
style: { opacity: 0.8 }
:The text was updated successfully, but these errors were encountered: