-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Display Bug On iOS about BoxView that under initial InVisible Layout #22897
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
Is it because the BoxView width is not set? |
Or Binding the isVisible param to Boxview |
Verified this issue with Visual Studio 17.11.0 Preview 1.1(8.0.40) can repro it but(8.0.21 &8.0.3) cannot repro. |
temp workaround:
|
Maybe change the BackgroundColor to Color will fix. |
Description
Each element of Options has an underline at the bottom。
①、②、③
On
RadioButton,the underline in options was not shown at all.But when I bring the app back to the foreground from the background, or scroll the CollectionView, the underline reappears.
I suspect that iOS is not rendering in time.
When I keep updating the selection of RadioButton and scrolling CollectionView, there is a probability that all option elements are covered together.
This is obviously a very serious display problem.
Steps to Reproduce
No response
Link to public reproduction project repository
https://github.com/maonaoda/MauiDisplayBugOnIOS
Version with bug
8.0.40 SR5
Is this a regression from previous behavior?
Yes, this used to work in Xamarin.Forms, Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: