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
FlyoutPage Shadow works incorrectly on iOS #22169
Labels
Comments
Closed
/similarissues |
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:
|
kubaflo
added a commit
to kubaflo/maui
that referenced
this issue
May 12, 2024
PureWeen
pushed a commit
that referenced
this issue
May 13, 2024
* Fixed #22169 * Update PhoneFlyoutPageRenderer.cs * Code refactor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
There are 3 examples of Shadow defects with FlyoutPage and PhoneFlyoutPageRenderer:
https://github.com/dotnet/maui/assets/18734152/645edae0-dc59-4a18-b290-c8b880634f0a
https://github.com/dotnet/maui/assets/18734152/c257901b-b0e8-4bb7-a335-736344aa7c82
https://github.com/dotnet/maui/assets/18734152/eef9996e-2887-4c06-ad99-eebf229a793a
You can see next defects:
When we have LeftToRight flow direction:
When we have RightToLeft flow direction:
Steps to Reproduce
Expected Result
Link to public reproduction project repository
No response
Version with bug
8.0.21 SR4.1
Is this a regression from previous behavior?
No, this is something new
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
No response
Did you find any workaround?
Not yet, but earlier on Xamarin I created own PhoneMasterDetailRenderer to fix these defects, because most of methods are hidden for inherit
Relevant log output
No response
The text was updated successfully, but these errors were encountered: