-
Notifications
You must be signed in to change notification settings - Fork 116
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
Rendering problem on iOS 10 #10
Comments
@junedomingo can you share the code for the above ? It's working fine for me. |
Custom styles are inlined for now.
|
@kirankalyan5, This is already in |
I guess this is React Native bug on iOS, even this simple piece of codes will have the same issue: text |
|
This glitch is visible only when your side border radius is greater than 0 and you have an element on its side with borders. I've disabled the left/right border and works for me (iOS 10.2.1 device). Try to disable the border left/right width on L51/52:
@kirankalyan5 if it's ok for you I can submit a PR. |
This appears to be a bug with React Native itself. Many people have reported similar issues:
|
@here - I have published the latest version, have a look! |
@kirankalyan5 I've tested with the latest version and the problem is still there |
I still got that problem after upgrade to Expo's SDK 18. |
Still have this problem too Example:
EDIT:Fixed it by doing this (??????)
|
Note with this fix, if there are only two tabs, there is no border between them. |
@kennykswan I agree, but when it's two tabs I don't find a need of border between them. |
This resolved it for me: tabStyle={[
tabStyle,
index !== 0 && index !== values.length - 1
? { marginLeft: Platform.OS === "ios" ? -1 : 0 }
: {}
]} |
hello guys, |
Hi guys,
|
I got rid of the artefact in by using Math.round in borderRadius provided directly to SegmentedControlTab. Apparently it doesn't like floats. This is certainly an iOS-only problem |
@kirankalyan5 @junedomingo Still getting this issue in ios 6s device with 2 tabs. |
Here you can see some shadow effect in the inactive tab.
this happens in actual device
The text was updated successfully, but these errors were encountered: