-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
bug: iOS: ion-slide elements will not render until a touch event happens #19413
Comments
Same Problem |
I have a similar problem. The element is in the correct position, but does not display properly |
I cannot reproduce anymore since upgrading to 4.11.8 - I cannot tell whether this has been silently fixed in one of the versions between 4.9.0 and the latest |
Closing this issue, since it is resolved for me and there is no feedback from the mentioned users. |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Bug Report
Ionic version:
[x] 4.9.0
Current behavior:
When using
<ion-slides>
within an Angular project, sometimes slide contents will not be rendered. Especially when they are composed out of more complex components and changing changing based on bound variables.The component will not render itself until a touch event happens. Changes go undetected by Angular and there are also no events (mutation observer) fired by the Swiper API (if observers and observers for children are enabled).
Once I manually trigger a touch event, the components within
<ion-slide>
elements will properly render.Expected behavior:
Slides, sub components and their children should always render.
Steps to reproduce:
Related code:
Other information:
This may be related to #19311
This does not happen with text only components, but with any images and SVGs.
This behaviour weirdly also extends to other components than elements. We have a custom countdown timer which exposes the same behaviour (which may or may not be related to this - but if - it's likely some weird Angular problem?!)
Ionic info:
The text was updated successfully, but these errors were encountered: