SfTextInputLayout hint stopped working correctly

[Michael Yui Fai Poon]

When entry inside SfTextInputLayout is bound to an object's property (object.property), when property is updated with property notify, the SfTextInputLayout's hint text stays as if no text was sent to the entry.

When I click on the entry however, then the entry text gets revealed correctly, and hint moves upwards, which it should have done on the moment the property got updated, not when we manually click.

Just to reiterate, the binding works correctly, and entry does get the data, it's the hint of SfTextInputLayout that doesn't go away anymore when there is a new value in the entry - requiring a user to tap the entry.

This only happened when I updated all my Syncfusion nuget packages from 18.3.0.42 to 18.4.0.31.

This only happens on Android too - used Android 10.0 - API 29 on a simulator, I am not sure about other ver sions of android.

[Sridevi Sivakumar]

Hi Michael Yui Fai Poon,

Greetings from Syncfusion.

We have prepared a sample to replicate the issue based on the provided details, but we are afraid, that we are not able to reproduce the issue at our end. The sample we tried can be downloaded from the below location.

Link: https://www.syncfusion.com/downloads/support/forum/160885/ze/BindIssueSample380397982



Since we are not aware of your exact application scenario, we were not able to reproduce this at our end, can you please share the below details, it will be helpful for us to analyze further and provide an appropriate solution?

Are you bind the value to the entry with some time delay?

Have you added the control inside any layout?

Can you share the  Xamarin.Forms version that is used in the application?

Have you checked the reported issue with any other device?

Please check the shared sample and if the issue still persists please modify the same with the issue reproducing step or else share the issue reproducing code snippet.

Regards,
Sridevi S. 

 

[Michael Yui Fai Poon]

Hi Michael Yui Fai Poon,

Greetings from Syncfusion.

We have prepared a sample to replicate the issue based on the provided details, but we are afraid, that we are not able to reproduce the issue at our end. The sample we tried can be downloaded from the below location.

Link: https://www.syncfusion.com/downloads/support/forum/160885/ze/BindIssueSample380397982



Since we are not aware of your exact application scenario, we were not able to reproduce this at our end, can you please share the below details, it will be helpful for us to analyze further and provide an appropriate solution?

Are you bind the value to the entry with some time delay?

Have you added the control inside any layout?

Can you share the  Xamarin.Forms version that is used in the application?

Have you checked the reported issue with any other device?

Please check the shared sample and if the issue still persists please modify the same with the issue reproducing step or else share the issue reproducing code snippet.

Regards,
Sridevi S. 

 

Found the issue!

This page failed to submit my reply, so trying again...

To replicate, set SfInputLayout to invisible through binding

Set Entry text through binding

Make SfInputLayout visible.

I was not able to upload sample due to size limit, so here's the code:

     <inputLayout:SfTextInputLayout  Hint="Name"   AutomationId="address_line_1L"  ContainerType="Outlined" IsVisible="{Binding ShowEntry}">
            <Entry Text="{Binding Asda, Mode=TwoWay}"  ReturnType="Next" AutomationId="address_line_1" TextChanged="Entry_TextChanged_1" />
        </inputLayout:SfTextInputLayout>

        <Button Text="Update Model Value" Clicked="Button_Clicked" />

       private void Button_Clicked(object sender, EventArgs e)
        {
            vm.Asda = "New value";
            vm.ShowEntry = true;
        }

[Michael Yui Fai Poon]

After removing files from obj and bin folder, I can finally attach.

Attachment: LayoutSample_3b000836.zip

[Sridevi Sivakumar]

Hi  Michael Yui Fai Poon,

Sorry for the inconvenience caused.

We have checked the reported problem with the provided sample and able to reproduce the issue and found the root cause for the same, and we will include this fix in our next weekly NuGet release, which is expected to be rolled out by December 29, 2020.

Please let us know if you need any further assistance.

Regards,
Sridevi S. 

[Sridevi Sivakumar]

Hi Michael Yui Fai Poon,

Our weekly release has been postponed to tomorrow(Dec 30th,2020). We will provide the fix by tomorrow. We will appreciate your patience until then.

Regards,
Sridevi S.  

[Sridevi Sivakumar]

Hi Michael Yui Fai Poon,

We are glad to announce that our weekly NuGet was rolled out and fix for the reported issue was included in the weekly NuGet.

NuGet Version: 18.4.0.32

We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.

Regards, 
Sridevi S  

[Michael Yui Fai Poon]

Hi Michael Yui Fai Poon,

We are glad to announce that our weekly NuGet was rolled out and fix for the reported issue was included in the weekly NuGet.

NuGet Version: 18.4.0.32

We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.

Regards, 
Sridevi S  

Thanks for keeping this up to date. I have tried the latest (18.4.0.32) in my project and it solved the problem.

Thank you.

[Sridevi Sivakumar]

Hi Michael Yui Fai Poon,

Thanks for your update.

We are glad that the reported problem resolved at your end.

Let us know if you need any further assistance.

Regards,
Sridevi S.