[Bug][iOS] CollectionView footer causes focused row to scroll off screen when the Keyboard opens

[lobbo232]

Description

Found whilst looking for a workaround for issue #9691.

If you have a footer at the bottom of a CollectionView, when clicking on an entry within the CollectionView and the keyboard opens the UI scrolls the additional height of the footer through the CollectionView and moves the tapped entry off the screen.

Steps to Reproduce

1. Create a new Xamarin.Forms app
2. Create a CollectionView with a bound collection of at least 20 items with the DataTemplate containing an Entry.
3. Add a CollectionView.Footer of a StackLayout with of a HeightRequest="1000"
4. Run the app and tap any of Entry that isn't near the bottom (first Entry works fine).
5. The focused Entry will be moved off the top of the screen.

Expected Behavior

The focused entry should be focused above the keyboard so the user can see what they type.

Actual Behavior

The focused entry is scrolled off the top of the screen.

Basic Information

• Version with issue: 4.4.0.991640
• Last known good version: Unknown
• IDE: Visual Studio 2019
• Platform Target Frameworks:
  • iOS: 13.10.0.17
  • Android: 10.1.3.7
  • UWP:
• Android Support Library Version:
• Nuget Packages:
• Affected Devices: iOS

Screenshots

TAP ITEM 1

Reproduction Link

Test Footer Causes Elements Out Of Focus.zip

Workaround

[lobbo232]

After a bit more playing around with this, it seems that with a HieghtRequest of 1000 on the footer content, an iPhone X running iOS 13 is fine, however an iPhone 6 running iOS 12 is not. It might be because the height of the footer is more noticeable on the smaller screen of an iPhone 6

[jsuarezruiz]

@lobbo232 I am going to close #9691 because it is the same issue, ok?

[lobbo232]

@jsuarezruiz While they are both related to CollectionView scrolling, I don't think they are the same issue.
#9691 is an issue caused by the keyboard obstructing items in a CollectionView.
#9706 is an issue caused by the height of a footer not being taken in to account when focusing an item in a CollectionView.

If you've confirmed both and are happy they're caused by the same thing, then go ahead.

[jsuarezruiz]

I think the cause could be the same, but I will relate and keep them until be 100% sure.

[rhodesRowan]

why has this been removed? This is a really urgent issue for many people