xamarin / Xamarin.Forms

Xamarin.Forms is no longer supported. Migrate your apps to .NET MAUI.
https://aka.ms/xamarin-upgrade
Other
5.62k stars 1.87k forks source link

[XF] Entry inside Expanded View Cell not working properly #3964

Open ferbeltran opened 6 years ago

ferbeltran commented 6 years ago

Description

A Entry inside a Expanded ViewCell doesnt behave properly: It doesnt respond the first time you tap it, and then closes the Keyboard (Numeric) after every numeric input

Just affecting Xamarin Forms under iOS

Steps to Reproduce

  1. Create a Custom ViewCell that expands upon tapping
  2. Place the entry in the expanded section of the viewcell
  3. When ViewCell is expanded, tap Entry

Expected Behavior

Tap the Custom ViewCell to expand and show the Entry control. Entry must show Soft Keyboard on first tap and should stay open until "Done" button is pressed

Actual Behavior

Tapping the ViewCell expands itself and shows Entry control, but Entry doesnt respond to first tap to show soft Keyboard. Upon 2nd tap it shows it but just to close after every number pressed

Basic Information

Screenshots

Reproduction Link

Works fine using XF 3.1 https://streamable.com/w9j12

Doesnt work using XF 3.2 It doesnt show in this video but i am tapping the entry TWICE for the Keyboard to appear https://streamable.com/yzn3w

hartez commented 6 years ago

Create a Custom ViewCell that expands upon tapping

@ferbeltran

Can you provide us with some more detail on how your custom ViewCell works? If you could provide code, that would make it easier for us to diagnose this issue.

hartez commented 6 years ago

@ferbeltran Never mind, we've got a solid reproduction of this bug at #4067.

itsTurk commented 5 years ago

I am experiencing this issue on iOS both in 3.3.0.967583 and the latest prerelease, 3.4.0.987044-pre1 I can confirm the issue does not exist on Xamarin.Forms 3.1.0.697729. Looking forward to a fix.

james1301 commented 5 years ago

Is there any kind of workaround for this? This is making my form quite unusable and I cannot find a solution to get round it.

tomaustin700 commented 5 years ago

We are also having this problem. This needs fixing or a workaround provided.

JamesBrining commented 5 years ago

This is becoming a real issue for us - please look into this ASAP

andyr79 commented 5 years ago

Also a big issue for us too, please escalate