-
Notifications
You must be signed in to change notification settings - Fork 688
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
[iOS] PipsPager breaks app layout #16715
Comments
Looks to be the same/related to unoplatform/uno.toolkit.ui#1125 |
This doesn't look to be related to SafeArea or SelectorExtensions. It seems to be an issue specific to PipsPager. If I create a simple all with just a PipsPager and attempt to change pips, I see the behavior: MainPage.xaml <Page x:Class="PipsApp.MainPage"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="using:PipsApp"
Background="{ThemeResource ApplicationPageBackgroundThemeBrush}">
<Grid Background="Red">
<PipsPager Background="Green"
HorizontalAlignment="Center"
Margin="0,50,0,0"
NumberOfPages="10"
x:Name="FlipViewPipsPager" />
</Grid>
</Page> Screen.Recording.2024-05-13.at.10.04.54.PM.mov |
Simple repro app |
@mcocaroUX Would you be able to confirm that this is no longer occurring as of the Uno.Sdk version 5.3.0-dev.1256? |
@kazo0 Issue is fixed on 5.3.0-dev.1256. Thank you! |
@kazo0 do we need to backport something for 5.2 stable? |
@agneszitte the changes implied cannot be backported, it's related to lifecycle changes. |
Current behavior
Currently when having a PipsPager+FlipView linked by SelectorExtensions at a Page and its changes it selected value, safe area (bottom and top) turns black. I could reproduce this only on iOS
Before sliding:
After sliding:
Expected behavior
Safe area should not be affected
How to reproduce it (as minimally and precisely as possible)
FlipViewSafeArea.zip
Run sample
Flip to show next image
Notice how safe area turns black
Environment
Package Version(s):
Uno.Sdk: 5.2.108
Visual Studio:
Relevant plugins:
Anything else we need to know?
The text was updated successfully, but these errors were encountered: