Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

ios:Page.UseSafeArea="true" makes the content of a page jumping on appearing XF 4.8 [Bug] [IOs] [Shell] #11777

Closed
Sasha111ua opened this issue Aug 13, 2020 · 4 comments
Labels
a/shell 🐚 e/3 🕒 3 in-progress This issue has an associated pull request that may resolve it! p/iOS 🍎 s/unverified New report that has yet to be verified t/bug 🐛

Comments

@Sasha111ua
Copy link

Description

If you use ios:Page.UseSafeArea="true" on a page then content jumps from unsafe area to safe area after page appeared. You basically can see that. On 4.7. works fine.

Steps to Reproduce

  1. Run project
  2. Click on any item of the list
  3. When ItemsDeails page appears you see like adjusting of the content layout is happening (jumping effect).

Expected Behavior

The page appears with content inside safe area

Actual Behavior

Layout adjustment happens after the page appeared.

Basic Information

  • Version with issue: 4.8.0.12.69
  • Last known good version: 4.7.0.968
  • IDE:
  • Platform Target Frameworks:
    • iOS:
  • Affected Devices: simulator and device

Reproduction Link

https://drive.google.com/file/d/1gCgWQ6oAi09EdAkxJk22a_kvnazqU94W/view?usp=sharing

@Sasha111ua Sasha111ua added s/unverified New report that has yet to be verified t/bug 🐛 labels Aug 13, 2020
@Sasha111ua Sasha111ua changed the title ios:Page.UseSafeArea="true" makes the content of a page jumping on appearing XF 4.8 [Bug] [IOs] ios:Page.UseSafeArea="true" makes the content of a page jumping on appearing XF 4.8 [Bug] [IOs] [Shell] Aug 13, 2020
@rmarinho
Copy link
Member

This is similar to #11723 it seems.

@Tommigun1980
Copy link

Tommigun1980 commented Aug 15, 2020

I noticed earlier that reading the safe area rectangle only gives values in OnAppearing (and not in the constructor as Xamarin.Forms's documentation claims). I filed a documentation bug report, which may already have been resolved, but maybe the functionality itself has changed in 4.8 and it was accessible in the constructor earlier? That would explain the flipping people see and why some plugins I am using are broken regarding the safe area.

@rs-mobitech
Copy link

How is it possible the Xamarin team missed something as obvious as this :-( Makes me feel like it is the users who are the testers and they just release code and hope for the best. I hope that things can improve but based on the last few years I think it will always be the same. Poor quality control of new releases and hundreds of unfixed bugs while the devs try to add more and more new features.

samhouts pushed a commit that referenced this issue Aug 25, 2020
… xplat elements (#11791)

* Disconnect renderer before disposing of it

* - fix ui test

* - remove any processing animations

* - cleanup code

* - fix ui test and add null checks

* - include android

fixes #11784
fixes #11777
@samhouts
Copy link
Member

closed by #11791

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
a/shell 🐚 e/3 🕒 3 in-progress This issue has an associated pull request that may resolve it! p/iOS 🍎 s/unverified New report that has yet to be verified t/bug 🐛
Projects
None yet
Development

No branches or pull requests

5 participants