-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Artifacts on View with borderRadius on only 2 corners on iOS #17998
Comments
Setting borderRadius to decimal also results in incorrect behaviour (only on iOS) Reproducible Demo Environment: Packages: (wanted => installed) |
this is still happening, anyone got a workaround? |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions. |
#19451 fixes the issue, but no status on merging this |
Revisit after this PR merged to RN - facebook/react-native#19451
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
Is this a bug report?
This is a bug
Environment
OS: macOS Sierra 10.12.6
Node: 7.6.0
Yarn: 1.3.2
npm: 4.1.2
Watchman: 4.7.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: Not Found
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.53.0 => 0.53.0
Steps to Reproduce
Run this on iOS device
Expected Behavior
Actual Behavior
Reproducible Demo
It was said in 11987 thats this was fixed, though it still continues #11897
The text was updated successfully, but these errors were encountered: