Bug 43993 - iOS: ListView size does not return to normal after keyboard disappears
Summary: iOS: ListView size does not return to normal after keyboard disappears
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms (show other bugs)
Version: 2.3.2
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
: 44604 (view as bug list)
Depends on:
Reported: 2016-09-05 03:52 UTC by adrianknight89
Modified: 2016-12-20 01:44 UTC (History)
6 users (show)

See Also:
Is this bug a regression?: ---
Last known good build:

repro (164.82 KB, application/zip)
2016-09-05 03:52 UTC, adrianknight89

Description adrianknight89 2016-09-05 03:52:45 UTC
Created attachment 17330 [details]

Please see repro.

When keyboard shows for an entry, it resizes the listview. When the keyboard is hidden, listview size does not return to normal on iOS.

Steps to reproduce:

1) Observe that item 99 on the list can be seen at the bottom
2) Hit entry area to display keyboard
3) Hide keyboard
4) Observe that several items at the bottom of the list cannot be navigated to because the listview size has increased.
Comment 1 adrianknight89 2016-09-05 05:35:49 UTC
If you put the page in a navigation page AND the navigation bar is visible, then this issue is not present. However, I need to hide the navigation bar so for me this is a big issue.
Comment 2 adrianknight89 2016-09-05 17:11:31 UTC
The issue was introduced in If you revert to, then you won't see it.
Comment 3 adrianknight89 2016-09-06 21:41:00 UTC
This PR fixes the issue: https://github.com/xamarin/Xamarin.Forms/pull/333
Comment 4 Rui Marinho 2016-10-04 16:33:19 UTC
This should be fixed in 2.3.2 hot fix 2, and 2.3.3-pre4
Comment 5 Matthew 2016-10-18 14:23:08 UTC
You really saved my bacon on fixing this, just discovered it today in stable!
Comment 6 Parmendra Kumar 2016-11-03 13:02:09 UTC
I have also checked this issue with Xamarin.Forms 2.3.3-pre3 and its working fine.

Hence closing this issue.
Comment 7 Samantha Houts [MSFT] 2016-12-20 01:44:23 UTC
*** Bug 44604 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.